Monitoring and locating tracked objects using audio/video recording and communication devices

ABSTRACT

Monitoring and locating tracked objects using audio/video (A/V) recording and communication devices in accordance with various embodiments of the present disclosure are provided. In one embodiment, a method for monitoring an object using a smart-home hub device in network communication with A/V recording and communication devices is provided, the method comprising: associating a tag having tag data compatible for use in a low-power wide-area network (LPWAN) with at least one tracked object to be located when missing; activating the smart-home hub device to monitor the at least one tracked object on a premises by listening for the tag data transmitted by the tag; determining when the at least one tracked object has been removed from the premises using the tag data; and transmitting to a first client device, an alert upon a determination that the at least one tracked object has been removed from the premises.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to provisional application Ser. No.62/550,976, filed on Aug. 28, 2017, the entire contents of which arehereby incorporated by reference.

TECHNICAL FIELD

The present embodiments relate to audio/video (AN) recording andcommunication devices, including A/V recording and communicationdoorbell systems. In particular, the present embodiments relate toimprovements in the functionality of A/V recording and communicationdevices that strengthen the ability of such devices to reduce crime andenhance public safety.

BACKGROUND

Home security is a concern for many homeowners and renters. Thoseseeking to protect or monitor their homes often wish to have video andaudio communications with visitors, for example, those visiting anexternal door or entryway. AudioNideo (A/V) recording and communicationdevices, such as doorbells, provide this functionality, and can also aidin crime detection and prevention. For example, audio and/or videocaptured by an A/V recording and communication device can be uploaded tothe cloud and recorded on a remote server. Subsequent review of the A/Vfootage can aid law enforcement in capturing perpetrators of homeburglaries and other crimes. Further, the presence of one or more A/Vrecording and communication devices on the exterior of a home, such as adoorbell unit at the entrance to the home, acts as a powerful deterrentagainst would-be burglars.

SUMMARY

The various embodiments of the present monitoring and locating trackedobjects using audio/video (A/V) recording and communication devices haveseveral features, no single one of which is solely responsible for theirdesirable attributes. Without limiting the scope of the presentembodiments as expressed by the claims that follow, their more prominentfeatures now will be discussed briefly. After considering thisdiscussion, and particularly after reading the section entitled“Detailed Description,” one will understand how the features of thepresent embodiments provide the advantages described herein.

One aspect of the present embodiments includes the realization thatobjects may be misplaced, stolen, or kidnapped. For example, inanimateobjects, such as jewelry, bicycles, vehicles, etc., or evenanimate/living objects, such as people or pets, may be removed and/orstolen from a user's premises. It would be advantageous, therefore, ifthe functionality of A/V recording and communication devices could beleveraged to monitor and locate objects, and/or identify and apprehendsuspected thieves and kidnappers. The present embodiments solve thisproblem by providing a long-range tag device that may be secured to anobject (may also be referred to as a “tracked object”) for monitoringabout a user's premises. In various embodiments, the tag device maytransmit tag data, where the tag device may be compatible for use in alow-power wide-area network (LPWAN) having long-range communicationscapabilities at a low bit rate. Further, a smart-home hub device and/ora first A/V recording and communication device may be configured toreceive the tag data and determine when the tracked object has beenremoved from the premises using the tag data. In addition, a trackedobject may be located using the tag device secured to the trackedobject. For example, if the tracked object is determined to be missingand/or stolen, a backend server may transmit the tag data to one or moresecond A/V recording and communication devices, located in variouslocations. The tracked object may be located when the tag dataassociated with the tracked object is captured by one of the second A/Vrecording and communication devices. Further, upon locating a trackedobject, the second A/V recording and communication device may captureimage data of the tracked object and/or the suspected thief of thetracked object. These and other aspects and advantages of the presentembodiments are described in further detail below.

In a first aspect, a method for monitoring an object using a smart-homehub device in network communication with audio/video (A/V) recording andcommunication devices is provided, the method comprising: associating,by the smart-home hub device, a tag having tag data compatible for usein a LPWAN with at least one tracked object to be located when missing,wherein the tag is configured to transmit the tag data using acommunication module; activating the smart-home hub device to monitorthe at least one tracked object on a premises by listening for the tagdata transmitted by the tag; determining when the at least one trackedobject has been removed from the premises using the tag data; andtransmitting, from the smart-home hub device, to a first client deviceassociated with a first A/V recording and communication device, an alertupon a determination that the at least one tracked object has beenremoved from the premises.

In an embodiment of the first aspect, the method further comprisesdetermining that the at least one tracked object has been removed fromthe premises when the tag data transmitted by the tag is not received bythe smart-home hub device within a predetermined amount of time.

In another embodiment of the first aspect, the method further comprisesreceiving the tag data, from the tag, at the smart-home hub device,wherein the tag data includes location data and determining that the atleast one tracked object has been removed from the premises when thelocation data indicates that the tag is beyond a perimeter of thepremises.

In another embodiment of the first aspect, the method further comprisesreceiving the tag data, from the tag, at the smart-home hub device,wherein the tag data includes location data, and determining that the atleast one tracked object has been removed from the premises when thelocation data indicates that the tag is moving away from the smart-homehub device.

In another embodiment of the first aspect, the tag is configured totransmit the tag data using chirp spread spectrum (CSS) modulationtechniques.

In another embodiment of the first aspect, the smart-home hub devicecomprises a communication module configured to receive the tag datausing CSS demodulation techniques.

In another embodiment of the first aspect, the tag data is LoRa data.

In another embodiment of the first aspect, the tag is a LoRa trackerconfigured to transmit the LoRa data.

In another embodiment of the first aspect, the smart-home hub devicecomprises a communication module configured to receive LoRa data.

In another embodiment of the first aspect, the tag is configured totransmit the tag data using ultra narrowband (UNB) modulationtechniques.

In another embodiment of the first aspect, the smart-home hub devicecomprises a communication module configured to receive the tag datausing UNB demodulation techniques.

In another embodiment of the first aspect, the method further comprisestransmitting, from the smart-home hub device, to a backend server, anoutput signal that includes the tag data and identifies the at least onetracked object as missing.

In a second aspect, a method for monitoring an object using audio/video(A/V) recording and communication devices is provided, the methodcomprising: receiving, from a smart-home hub device, at a backendserver, an output signal that includes tag data compatible for use in alow-power wide-area network (LPWAN), wherein the output signalidentifies at least one tracked object as missing; transmitting, fromthe backend server, to a plurality of A/V recording and communicationdevices, a locate object signal that includes the tag data and a commandto locate the at least one tracked object using the tag data; receiving,from one of the plurality of A/V recording and communication devices,image data of the at least one tracked object captured using a camera ofthe one of the plurality of second A/V recording and communicationdevices; and transmitting, from the backend server to a client deviceassociated with the smart-home hub device, an object found signalcomprising the image data of the at least one tracked object.

In an embodiment of the second aspect, the method further comprisestransmitting, from the backend server, to the one of the plurality ofA/V recording and communication devices, a power-up command signalwherein the power-up command signal configures the one of the pluralityof A/V recording and communication devices to power up the camera andcapture the image data of the at least one tracked object.

In another embodiment of the second aspect, the image data includesimages of a suspected thief of the at least one tracked object.

In another embodiment of the second aspect, each of the plurality of A/Vrecording and communication devices comprises a communication moduleconfigured to receive the tag data using chirp spread spectrum (CSS)demodulation techniques.

In another embodiment of the second aspect, the tag data is LoRa data.

In another embodiment of the second aspect, each of the plurality of A/Vrecording and communication devices comprises a communication moduleconfigured to receive LoRa data.

In another embodiment of the second aspect, each of the plurality of A/Vrecording and communication devices comprises a communication moduleconfigured to receive tag data using ultra narrowband (UNB) demodulationtechniques.

In a third aspect, a method for monitoring an object using audio/video(A/V) recording and communication devices is provided, the methodcomprising: receiving, from a first A/V recording and communicationdevice, at a backend server, an output signal that includes tag datacompatible for use in a low-power wide-area network (LPWAN), wherein theoutput signal identifies at least one tracked object as missing;transmitting, from the backend server, to a plurality of second A/Vrecording and communication devices, a locate object signal thatincludes the tag data and a command to locate the at least one trackedobject using the tag data; receiving, from one of the plurality ofsecond A/V recording and communication devices, second image data thatincludes image data of the at least one tracked object captured using acamera of the one of the plurality of second A/V recording andcommunication devices; and transmitting, from the backend server to aclient device associated with the first A/V recording and communicationdevice, an object found signal comprising the second image data thatincludes the image data of the at least one tracked object.

In an embodiment of the third aspect, the method further comprisestransmitting, from the backend server, to the one of the plurality ofsecond A/V recording and communication devices, a power-up commandsignal wherein the power-up command signal configures the one of theplurality of second A/V recording and communication devices to power upthe camera and capture the second image data that includes the imagedata of the at least one tracked object.

In another embodiment of the third aspect, the second image dataincludes images of a suspected thief of the at least one tracked object.

In another embodiment of the third aspect, each of the plurality ofsecond A/V recording and communication devices comprises a communicationmodule configured to receive the tag data using chirp spread spectrum(CSS) demodulation techniques.

In another embodiment of the third aspect, the tag data is LoRa data.

In another embodiment of the third aspect, each of the plurality ofsecond A/V recording and communication devices comprises a communicationmodule configured to receive LoRa data.

In another embodiment of the third aspect, each of the plurality ofsecond A/V recording and communication devices comprises a communicationmodule configured to receive tag data using ultra narrowband (UNB)demodulation techniques.

In a fourth aspect, a method for locating a missing object using anaudio/video (A/V) recording and communication device is provided, theA/V recording and communication device including a camera and acommunication module, the method comprising: receiving, from a backendserver, using the communication module, a locate object signal thatidentifies a tracked object as missing, wherein the locate object signalincludes tag data compatible for use in a low-power wide-area network(LPWAN) and a command to locate the tracked object using the tag data;listening for, and detecting, using the communication module, the tagdata transmitted by the tag; recording, using the camera, image datathat includes image data of the tracked object; and transmitting, to thebackend server, an object found signal comprising the image data thatincludes the image data of the tracked object.

Another embodiment of the fourth aspect further comprises receiving,from the backend server, a power-up command signal wherein the power-upcommand signal configures the A/V recording and communication device topower up the camera and capture the image data that includes the imagedata of the tracked object.

In another embodiment of the fourth aspect, the image data includesimages of a suspected thief of the tracked object.

BRIEF DESCRIPTION OF THE DRAWINGS

The various embodiments of the present monitoring and locating trackedobjects using audio/video (A/V) recording and communication devices nowwill be discussed in detail with an emphasis on highlighting theadvantageous features. These embodiments depict the novel andnon-obvious tracking and locating missing objects using A/V recordingand communication devices shown in the accompanying drawings, which arefor illustrative purposes only. These drawings include the followingfigures, in which like numerals indicate like parts:

FIG. 1 is a functional block diagram illustrating a system for streamingand storing A/V content captured by an audio/video (A/V) recording andcommunication device according to various aspects of the presentdisclosure;

FIG. 2 is a flowchart illustrating a process for streaming and storingA/V content from an A/V recording and communication device according tovarious aspects of the present disclosure;

FIG. 3 is a front view of an A/V recording and communication deviceaccording to various aspects of the present disclosure;

FIG. 4 is a rear view of the A/V recording and communication device ofFIG. 3;

FIG. 5 is a left side view of the A/V recording and communication deviceof FIG. 3 attached to a mounting bracket according to various aspects ofthe present disclosure;

FIG. 6 is cross-sectional right side view of the A/V recording andcommunication device of FIG. 3;

FIG. 7 is an exploded view of the A/V recording and communication deviceand the mounting bracket of FIG. 5;

FIG. 8 is a rear view of the mounting bracket of FIG. 5;

FIGS. 9 and 10 are top and bottom views, respectively, of the A/Vrecording and communication device and the mounting bracket of FIG. 5;

FIG. 11 is a top view of a passive infrared sensor assembly according tovarious aspects of the present disclosure;

FIG. 12 is a front view of the passive infrared sensor assembly of FIG.11;

FIG. 13 is a top view of the passive infrared sensor assembly of FIG.11, illustrating the fields of view of the passive infrared sensorsaccording to various aspects of the present disclosure;

FIG. 14 a functional block diagram of the components of the A/Vrecording and communication device of FIG. 3;

FIG. 15 is a functional block diagram illustrating a system forcommunicating in a network according to various aspects of the presentdisclosure;

FIG. 16 is a functional block diagram illustrating one embodiment of asmart-home hub device according to various aspects of the presentdisclosure;

FIG. 17 is a functional block diagram illustrating one embodiment of atag device according to various aspects of the present disclosure;

FIG. 18 is a functional block diagram illustrating one embodiment of afirst A/V recording and communication device according to variousaspects of the present disclosure;

FIG. 19 is a functional block diagram illustrating one embodiment of afirst client device according to various aspects of the presentdisclosure;

FIG. 20 is a functional block diagram illustrating one embodiment of asecond A/V recording and communication device according to variousaspects of the present disclosure;

FIG. 21 is a functional block diagram illustrating one embodiment of abackend device according to various aspects of the present disclosure;

FIG. 22 is a flowchart illustrating one embodiment of a process formonitoring an object on a premises according to an aspect of the presentdisclosure;

FIGS. 23-25 are flowcharts illustrating embodiments of processes fordetermining whether a tracked object has been removed from a premisesaccording to various aspects of the present disclosure;

FIG. 26 is a flowchart illustrating one embodiment of a process formonitoring and locating a tracked object according to an aspect of thepresent disclosure;

FIG. 27 is a flowchart illustrating one embodiment of a process forcapturing image data of a tracked object according to an aspect of thepresent disclosure;

FIGS. 28-29 are sequence diagrams illustrating embodiments of processesfor locating missing and/or stolen objects according to various aspectsof the present disclosure;

FIG. 30 is a functional block diagram of a client device on which thepresent embodiments may be implemented according to various aspects ofthe present disclosure; and

FIG. 31 is a functional block diagram of a general-purpose computingsystem on which the present embodiments may be implemented according tovarious aspects of present disclosure.

DETAILED DESCRIPTION

The following detailed description describes the present embodimentswith reference to the drawings. In the drawings, reference numbers labelelements of the present embodiments. These reference numbers arereproduced below in connection with the discussion of the correspondingdrawing features.

The embodiments of the present monitoring and locating tracked objectsusing audio/video (A/V) recording and communication devices aredescribed below with reference to the figures. These figures, and theirwritten descriptions, indicate that certain components of the apparatusare formed integrally, and certain other components are formed asseparate pieces. Those of ordinary skill in the art will appreciate thatcomponents shown and described herein as being formed integrally may inalternative embodiments be formed as separate pieces. Those of ordinaryskill in the art will further appreciate that components shown anddescribed herein as being formed as separate pieces may in alternativeembodiments be formed integrally. Further, as used herein the termintegral describes a single unitary piece.

With reference to FIG. 1, the present embodiments include an audio/video(A/V) device 100. While the present disclosure provides numerousexamples of methods and systems including A/V recording andcommunication doorbells, the present embodiments are equally applicablefor A/V recording and communication devices other than doorbells. Forexample, the present embodiments may include one or more A/V recordingand communication security cameras instead of, or in addition to, one ormore A/V recording and communication doorbells. An example A/V recordingand communication security camera may include substantially all of thestructure and/or functionality of the doorbells described herein, butwithout the front button and related components.

The A/V recording and communication device 100 may be located near theentrance to a structure (not shown), such as a dwelling, a business, astorage facility, etc. The A/V recording and communication device 100includes a camera 102, a microphone 104, and a speaker 106. The camera102 may comprise, for example, a high definition (HD) video camera, suchas one capable of capturing video images at an image display resolutionof 1080p or better. While not shown, the A/V recording and communicationdevice 100 may also include other hardware and/or components, such as ahousing, a communication module (which may facilitate wired and/orwireless communication with other devices), one or more motion sensors(and/or other types of sensors), a button, etc. The A/V recording andcommunication device 100 may further include similar componentry and/orfunctionality as the wireless communication doorbells described in USPatent Application Publication Nos. 2015/0022620 (application Ser. No.14/499,828) and 2015/0022618 (application Ser. No. 14/334,922), both ofwhich are incorporated herein by reference in their entireties as iffully set forth.

With further reference to FIG. 1, the A/V recording and communicationdevice 100 communicates with a user's network 110, which may be forexample a wired and/or wireless network. If the user's network 110 iswireless, or includes a wireless component, the network 110 may be aWi-Fi network compatible with the IEEE 802.11 standard and/or otherwireless communication standard(s). The user's network 110 is connectedto another network 112, which may comprise, for example, the Internetand/or a public switched telephone network (PSTN). As described below,the A/V recording and communication device 100 may communicate with theuser's client device 114 via the user's network 110 and the network 112(Internet/PSTN). The user's client device 114 may comprise, for example,a mobile telephone (may also be referred to as a cellular telephone),such as a smartphone, a personal digital assistant (PDA), or anothercommunication device. The user's client device 114 comprises a display(not shown) and related components capable of displaying streamingand/or recorded video images. The user's client device 114 may alsocomprise a speaker and related components capable of broadcastingstreaming and/or recorded audio, and may also comprise a microphone. TheA/V recording and communication device 100 may also communicate with oneor more remote storage device(s) 116 (may be referred to interchangeablyas “cloud storage device(s)”), one or more servers 118, and/or a backendAPI (application programming interface) 120 via the user's network 110and the network 112 (Internet/PSTN). While FIG. 1 illustrates thestorage device 116, the server 118, and the backend API 120 ascomponents separate from the network 112, it is to be understood thatthe storage device 116, the server 118, and/or the backend API 120 maybe considered to be components of the network 112.

The network 112 may be any wireless network or any wired network, or acombination thereof, configured to operatively couple theabove-mentioned modules, devices, and systems as shown in FIG. 1. Forexample, the network 112 may include one or more of the following: aPSTN (public switched telephone network), the Internet, a localintranet, a PAN (Personal Area Network), a LAN (Local Area Network), aWAN (Wide Area Network), a MAN (Metropolitan Area Network), a virtualprivate network (VPN), a storage area network (SAN), a frame relayconnection, an Advanced Intelligent Network (AIN) connection, asynchronous optical network (SONET) connection, a digital T1, T3, E1 orE3 line, a Digital Data Service (DDS) connection, a DSL (DigitalSubscriber Line) connection, an Ethernet connection, an ISDN (IntegratedServices Digital Network) line, a dial-up port such as a V.90, V.34, orV.34bis analog modem connection, a cable modem, an ATM (AsynchronousTransfer Mode) connection, or an FDDI (Fiber Distributed Data Interface)or CDDI (Copper Distributed Data Interface) connection. Furthermore,communications may also include links to any of a variety of wirelessnetworks, including WAP (Wireless Application Protocol), GPRS (GeneralPacket Radio Service), GSM (Global System for Mobile Communication),LTE, VoLTE, LoRaWAN, LPWAN, RPMA, LTE Cat-“X” (e.g. LTE Cat 1, LTE Cat0, LTE CatM1, LTE Cat NB1), CDMA (Code Division Multiple Access), TDMA(Time Division Multiple Access), FDMA (Frequency Division MultipleAccess), and/or OFDMA (Orthogonal Frequency Division Multiple Access)cellular phone networks, GPS, CDPD (cellular digital packet data), RIM(Research in Motion, Limited) duplex paging network, Bluetooth radio, oran IEEE 802.11-based radio frequency network. The network can furtherinclude or interface with any one or more of the following: RS-232serial connection, IEEE-1394 (Firewire) connection, Fibre Channelconnection, IrDA (infrared) port, SCSI (Small Computer SystemsInterface) connection, USB (Universal Serial Bus) connection, or otherwired or wireless, digital or analog, interface or connection, mesh orDigi® networking.

According to one or more aspects of the present embodiments, when aperson (may be referred to interchangeably as “visitor”) arrives at theA/V recording and communication device 100, the A/V recording andcommunication device 100 detects the visitor's presence and beginscapturing video images within a field of view of the camera 102. The A/Vcommunication device 100 may also capture audio through the microphone104. The A/V recording and communication device 100 may detect thevisitor's presence by detecting motion using the camera 102 and/or amotion sensor, and/or by detecting that the visitor has pressed a frontbutton of the A/V recording and communication device 100 (if the A/Vrecording and communication device 100 is a doorbell).

In response to the detection of the visitor, the A/V recording andcommunication device 100 sends an alert to the user's client device 114(FIG. 1) via the user's network 110 and the network 112. The A/Vrecording and communication device 100 also sends streaming video, andmay also send streaming audio, to the user's client device 114. If theuser answers the alert, two-way audio communication may then occurbetween the visitor and the user through the A/V recording andcommunication device 100 and the user's client device 114. The user mayview the visitor throughout the duration of the call, but the visitorcannot see the user (unless the A/V recording and communication device100 includes a display, which it may in some embodiments).

The video images captured by the camera 102 of the A/V recording andcommunication device 100 (and the audio captured by the microphone 104)may be uploaded to the cloud and recorded on the remote storage device116 (FIG. 1). In some embodiments, the video and/or audio may berecorded on the remote storage device 116 even if the user chooses toignore the alert sent to his or her client device 114.

With further reference to FIG. 1, the system may further comprise abackend API 120 including one or more components. A backend API(application programming interface) may comprise, for example, a server(e.g. a real server, or a virtual machine, or a machine running in acloud infrastructure as a service), or multiple servers networkedtogether, exposing at least one API to client(s) accessing it. Theseservers may include components such as application servers (e.g.software servers), depending upon what other components are included,such as a caching layer, or database layers, or other components. Abackend API may, for example, comprise many such applications, each ofwhich communicate with one another using their public APIs. In someembodiments, the API backend may hold the bulk of the user data andoffer the user management capabilities, leaving the clients to have verylimited state.

The backend API 120 illustrated FIG. 1 may include one or more APIs. AnAPI is a set of routines, protocols, and tools for building software andapplications. An API expresses a software component in terms of itsoperations, inputs, outputs, and underlying types, definingfunctionalities that are independent of their respectiveimplementations, which allows definitions and implementations to varywithout compromising the interface. Advantageously, an API may provide aprogrammer with access to an application's functionality without theprogrammer needing to modify the application itself, or even understandhow the application works. An API may be for a web-based system, anoperating system, or a database system, and it provides facilities todevelop applications for that system using a given programming language.In addition to accessing databases or computer hardware like hard diskdrives or video cards, an API can ease the work of programming GUIcomponents. For example, an API can facilitate integration of newfeatures into existing applications (a so-called “plug-in API”). An APIcan also assist otherwise distinct applications with sharing data, whichcan help to integrate and enhance the functionalities of theapplications.

The backend API 120 illustrated in FIG. 1 may further include one ormore services (also referred to as network services). A network serviceis an application that provides data storage, manipulation,presentation, communication, and/or other capability. Network servicesare often implemented using a client-server architecture based onapplication-layer network protocols. Each service may be provided by aserver component running on one or more computers (such as a dedicatedserver computer offering multiple services) and accessed via a networkby client components running on other devices. However, the client andserver components can both be run on the same machine. Clients andservers may have a user interface, and sometimes other hardwareassociated with them.

FIG. 2 is a flowchart illustrating a process for streaming and storingA/V content from the A/V recording and communication device 100according to various aspects of the present disclosure. At block B200,the A/V recording and communication device 100 detects the visitor'spresence and captures video images within a field of view of the camera102. The A/V recording and communication device 100 may also captureaudio through the microphone 104. As described above, the A/V recordingand communication device 100 may detect the visitor's presence bydetecting motion using the camera 102 and/or a motion sensor, and/or bydetecting that the visitor has pressed a front button of the A/Vrecording and communication device 100 (if the A/V recording andcommunication device 100 is a doorbell). Also as described above, thevideo recording/capture may begin when the visitor is detected, or maybegin earlier, as described below.

At block B202, a communication module of the A/V recording andcommunication device 100 sends a connection request, via the user'snetwork 110 and the network 112, to a device in the network 112. Forexample, the network device to which the request is sent may be a serversuch as the server 118. The server 118 may comprise a computer programand/or a machine that waits for requests from other machines or software(clients) and responds to them. A server typically processes data. Onepurpose of a server is to share data and/or hardware and/or softwareresources among clients. This architecture is called the client-servermodel. The clients may run on the same computer or may connect to theserver over a network. Examples of computing servers include databaseservers, file servers, mail servers, print servers, web servers, gameservers, and application servers. The term server may be construedbroadly to include any computerized process that shares a resource toone or more client processes. In another example, the network device towhich the request is sent may be an API such as the backend API 120,which is described above.

In response to the request, at block B204 the network device may connectthe A/V recording and communication device 100 to the user's clientdevice 114 through the user's network 110 and the network 112. At blockB206, the A/V recording and communication device 100 may recordavailable audio and/or video data using the camera 102, the microphone104, and/or any other device/sensor available. At block B208, the audioand/or video data is transmitted (streamed) from the A/V recording andcommunication device 100 to the user's client device 114 via the user'snetwork 110 and the network 112. At block B210, the user may receive anotification on his or her client device 114 with a prompt to eitheraccept or deny the call.

At block B212, the process determines whether the user has accepted ordenied the call. If the user denies the notification, then the processadvances to block B214, where the audio and/or video data is recordedand stored at a cloud server. The session then ends at block B216 andthe connection between the A/V recording and communication device 100and the user's client device 114 is terminated. If, however, the useraccepts the notification, then at block B218 the user communicates withthe visitor through the user's client device 114 while audio and/orvideo data captured by the camera 102, the microphone 104, and/or otherdevices/sensors is streamed to the user's client device 114. At the endof the call, the user may terminate the connection between the user'sclient device 114 and the A/V recording and communication device 100 andthe session ends at block B216. In some embodiments, the audio and/orvideo data may be recorded and stored at a cloud server (block B214)even if the user accepts the notification and communicates with thevisitor through the user's client device 114.

FIGS. 3-5 illustrate a wireless audio/video (A/V) communication doorbell130 according to an aspect of present embodiments. FIG. 3 is a frontview, FIG. 4 is a rear view, and FIG. 5 is a left side view of thedoorbell 130 coupled with a mounting bracket 137. The doorbell 130includes a faceplate 135 mounted to a back plate 139 (FIG. 4). Withreference to FIG. 5, the faceplate 135 has a substantially flat profile.The faceplate 135 may comprise any suitable material, including, withoutlimitation, metals, such as brushed aluminum or stainless steel, metalalloys, or plastics. The faceplate 135 protects the internal contents ofthe doorbell 130 and serves as an exterior front surface of the doorbell130.

With reference to FIG. 3, the faceplate 135 includes a button 133 and alight pipe 136. The button 133 and the light pipe 136 may have variousprofiles that may or may not match the profile of the faceplate 135. Thelight pipe 136 may comprise any suitable material, including, withoutlimitation, transparent plastic, that is capable of allowing lightproduced within the doorbell 130 to pass through. The light may beproduced by one or more light-emitting components, such aslight-emitting diodes (LED's), contained within the doorbell 130, asfurther described below. The button 133 may make contact with a buttonactuator (not shown) located within the doorbell 130 when the button 133is pressed by a visitor. When pressed, the button 133 may trigger one ormore functions of the doorbell 130, as further described below.

With reference to FIGS. 3 and 5, the doorbell 130 further includes anenclosure 131 that engages the faceplate 135. In the illustratedembodiment, the enclosure 131 abuts an upper edge 135T (FIG. 3) of thefaceplate 135, but in alternative embodiments one or more gaps betweenthe enclosure 131 and the faceplate 135 may facilitate the passage ofsound and/or light through the doorbell 130. The enclosure 131 maycomprise any suitable material, but in some embodiments the material ofthe enclosure 131 preferably permits infrared light to pass through frominside the doorbell 130 to the environment and vice versa. The doorbell130 further includes a lens 132. In some embodiments, the lens maycomprise a Fresnel lens, which may be patterned to deflect incominglight into one or more infrared sensors located within the doorbell 130.The doorbell 130 further includes a camera 134, which captures videodata when activated, as described below.

FIG. 4 is a rear view of the doorbell 130, according to an aspect of thepresent embodiments. As illustrated, the enclosure 131 may extend fromthe front of the doorbell 130 around to the back thereof and may fitsnugly around a lip of the back plate 139. The back plate 139 maycomprise any suitable material, including, without limitation, metals,such as brushed aluminum or stainless steel, metal alloys, or plastics.The back plate 139 protects the internal contents of the doorbell 130and serves as an exterior rear surface of the doorbell 130. Thefaceplate 135 may extend from the front of the doorbell 130 and at leastpartially wrap around the back plate 139, thereby allowing a coupledconnection between the faceplate 135 and the back plate 139. The backplate 139 may have indentations in its structure to facilitate thecoupling.

With further reference to FIG. 4, spring contacts 140 may provide powerto the doorbell 130 when mated with other conductive contacts connectedto a power source. The spring contacts 140 may comprise any suitableconductive material, including, without limitation, copper, and may becapable of deflecting when contacted by an inward force, for example theinsertion of a mating element. The doorbell 130 further comprises aconnector 160, such as a micro-USB or other connector, whereby powerand/or data may be supplied to and from the components within thedoorbell 130. A reset button 159 may be located on the back plate 139,and may make contact with a button actuator (not shown) located withinthe doorbell 130 when the reset button 159 is pressed. When the resetbutton 159 is pressed, it may trigger one or more functions, asdescribed below.

FIG. 5 is a left side profile view of the doorbell 130 coupled to themounting bracket 137, according to an aspect of the present embodiments.The mounting bracket 137 facilitates mounting the doorbell 130 to asurface, such as the exterior of a building, such as a home or office.As illustrated in FIG. 5, the faceplate 135 may extend from the bottomof the doorbell 130 up to just below the camera 134, and connect to theback plate 139 as described above. The lens 132 may extend and curlpartially around the side of the doorbell 130. The enclosure 131 mayextend and curl around the side and top of the doorbell 130, and may becoupled to the back plate 139 as described above. The camera 134 mayprotrude slightly through the enclosure 131, thereby giving it a widerfield of view. The mounting bracket 137 may couple with the back plate139 such that they contact each other at various points in a commonplane of contact, thereby creating an assembly including the doorbell130 and the mounting bracket 137. The couplings described in thisparagraph, and elsewhere, may be secured by, for example and withoutlimitation, screws, interference fittings, adhesives, or otherfasteners. Interference fittings may refer to a type of connection wherea material relies on pressure and/or gravity coupled with the material'sphysical strength to support a connection to a different element.

FIG. 6 is a right side cross-sectional view of the doorbell 130 withoutthe mounting bracket 137. In the illustrated embodiment, the lens 132 issubstantially coplanar with the front surface 131F of the enclosure 131.In alternative embodiments, the lens 132 may be recessed within theenclosure 131 or may protrude outward from the enclosure 131. The camera134 is coupled to a camera printed circuit board (PCB) 147, and a lens134 a of the camera 134 protrudes through an opening in the enclosure131. The camera lens 134 a may be a lens capable of focusing light intothe camera 134 so that clear images may be taken.

The camera PCB 147 may be secured within the doorbell with any suitablefasteners, such as screws, or interference connections, adhesives, etc.The camera PCB 147 comprises various components that enable thefunctionality of the camera 134 of the doorbell 130, as described below.Infrared light-emitting components, such as infrared LED's 168, arecoupled to the camera PCB 147 and may be triggered to activate when alight sensor detects a low level of ambient light. When activated, theinfrared LED's 168 may emit infrared light through the enclosure 131and/or the camera 134 out into the ambient environment. The camera 134,which may be configured to detect infrared light, may then capture thelight emitted by the infrared LED's 168 as it reflects off objectswithin the camera's 134 field of view, so that the doorbell 130 canclearly capture images at night (may be referred to as “night vision”).

With continued reference to FIG. 6, the doorbell 130 further comprises afront PCB 146, which in the illustrated embodiment resides in a lowerportion of the doorbell 130 adjacent a battery 166. The front PCB 146may be secured within the doorbell 130 with any suitable fasteners, suchas screws, or interference connections, adhesives, etc. The front PCB146 comprises various components that enable the functionality of theaudio and light components, as further described below. The battery 166may provide power to the doorbell 130 components while receiving powerfrom the spring contacts 140, thereby engaging in a trickle-chargemethod of power consumption and supply. Alternatively, the doorbell 130may draw power directly from the spring contacts 140 while relying onthe battery 166 only when the spring contacts 140 are not providing thepower necessary for all functions. Still further, the battery 166 maycomprise the sole source of power for the doorbell 130. In suchembodiments, the spring contacts 140 may not be connected to a source ofpower. When the battery 166 is depleted of its charge, it may berecharged, such as by connecting a power source to the connector 160.

With continued reference to FIG. 6, the doorbell 130 further comprises apower PCB 148, which in the illustrated embodiment resides behind thecamera PCB 147. The power PCB 148 may be secured within the doorbell 130with any suitable fasteners, such as screws, or interferenceconnections, adhesives, etc. The power PCB 148 comprises variouscomponents that enable the functionality of the power and device-controlcomponents, as further described below.

With continued reference to FIG. 6, the doorbell 130 further comprises acommunication module 164 coupled to the power PCB 148. The communicationmodule 164 facilitates communication with client devices in one or moreremote locations, as further described below. The connector 160 mayprotrude outward from the power PCB 148 and extend through a hole in theback plate 139. The doorbell 130 further comprises passive infrared(PIR) sensors 144, which are secured on or within a PIR sensor holder143, and the assembly resides behind the lens 132. In some embodiments,the doorbell 130 may comprise three PIR sensors 144, as furtherdescribed below, but in other embodiments any number of PIR sensors 144may be provided. The PIR sensor holder 143 may be secured to thedoorbell 130 with any suitable fasteners, such as screws, orinterference connections, adhesives, etc. The PIR sensors 144 may be anytype of sensor capable of detecting and communicating the presence of aheat source within their field of view. Further, alternative embodimentsmay comprise one or more motion sensors either in place of or inaddition to the PIR sensors 144. The motion sensors may be configured todetect motion using any methodology, such as a methodology that does notrely on detecting the presence of a heat source within a field of view.

FIG. 7 is an exploded view of the doorbell 130 and the mounting bracket137 according to an aspect of the present embodiments. The mountingbracket 137 is configured to be mounted to a mounting surface (notshown) of a structure, such as a home or an office. FIG. 7 shows thefront side 137F of the mounting bracket 137. The mounting bracket 137 isconfigured to be mounted to the mounting surface such that the back side137B thereof faces the mounting surface. In certain embodiments themounting bracket 137 may be mounted to surfaces of various composition,including, without limitation, wood, concrete, stucco, brick, vinylsiding, aluminum siding, etc., with any suitable fasteners, such asscrews, or interference connections, adhesives, etc. The doorbell 130may be coupled to the mounting bracket 137 with any suitable fasteners,such as screws, or interference connections, adhesives, etc.

With continued reference to FIG. 7, the illustrated embodiment of themounting bracket 137 includes the terminal screws 138. The terminalscrews 138 are configured to receive electrical wires adjacent themounting surface of the structure upon which the mounting bracket 137 ismounted, so that the doorbell 130 may receive electrical power from thestructure's electrical system. The terminal screws 138 are electricallyconnected to electrical contacts 177 of the mounting bracket. If poweris supplied to the terminal screws 138, then the electrical contacts 177also receive power through the terminal screws 138. The electricalcontacts 177 may comprise any suitable conductive material, including,without limitation, copper, and may protrude slightly from the face ofthe mounting bracket 137 so that they may mate with the spring contacts140 located on the back plate 139.

With reference to FIGS. 7 and 8 (which is a rear view of the mountingbracket 137), the mounting bracket 137 further comprises a bracket PCB149. With reference to FIG. 8, the bracket PCB 149 is situated outsidethe doorbell 130, and is therefore configured for various sensors thatmeasure ambient conditions, such as an accelerometer 150, a barometer151, a humidity sensor 152, and a temperature sensor 153. The functionsof these components are discussed in more detail below. The bracket PCB149 may be secured to the mounting bracket 137 with any suitablefasteners, such as screws, or interference connections, adhesives, etc.

FIGS. 9 and 10 are top and bottom views, respectively, of the doorbell130. As described above, the enclosure 131 may extend from the frontface 131F of the doorbell 130 to the back, where it contacts and snuglysurrounds the back plate 139. The camera 134 may protrude slightlybeyond the front face 131F of the enclosure 131, thereby giving thecamera 134 a wider field of view. The mounting bracket 137 may include asubstantially flat rear surface 137R, such that the doorbell 130 and themounting bracket 137 assembly may sit flush against the surface to whichthey are mounted. With reference to FIG. 10, the lower end of theenclosure 131 may include security screw apertures 141 configured toreceive screws or other fasteners.

FIG. 11 is a top view and FIG. 12 is a front view of a passive infraredsensor assembly 179 including the lens 132, the passive infrared sensorholder 143, the passive infrared sensors 144, and a flexible powercircuit 145. The passive infrared sensor holder 143 is configured tomount the passive infrared sensors 144 facing out through the lens 132at varying angles, thereby allowing the passive infrared sensor 144field of view to be expanded to 180° or more and also broken up intovarious zones, as further described below. The passive infrared sensorholder 143 may include one or more faces 178, including a center face178C and two side faces 178S to either side of the center face 178C.With reference to FIG. 12, each of the faces 178 defines an opening 181within or on which the passive infrared sensors 144 may be mounted. Inalternative embodiments, the faces 178 may not include openings 181, butmay instead comprise solid flat faces upon which the passive infraredsensors 144 may be mounted. Generally, the faces 178 may be any physicalstructure capable of housing and/or securing the passive infraredsensors 144 in place.

With reference to FIG. 11, the passive infrared sensor holder 143 may besecured to the rear face of the lens 132. The flexible power circuit 145may be any material or component capable of delivering power and/or datato and from the passive infrared sensors 144, and may be contoured toconform to the non-linear shape of the passive infrared sensor holder143. The flexible power circuit 145 may connect to, draw power from,and/or transmit data to and from, the power printed circuit board 148.

FIG. 13 is a top view of the passive infrared sensor assembly 179illustrating the fields of view of the passive infrared sensors 144. Inthe illustrated embodiment, the side faces 178S of the passive infraredsensor holder 143 are angled at 55° facing outward from the center face178C, and each passive infrared sensor 144 has a field of view of 110°.However, these angles may be increased or decreased as desired. Zone 1is the area that is visible only to a first one of the passive infraredsensors 144-1. Zone 2 is the area that is visible only to the firstpassive infrared sensor 144-1 and a second one of the passive infraredsensors 144-2. Zone 3 is the area that is visible only to the secondpassive infrared sensor 144-2. Zone 4 is the area that is visible onlyto the second passive infrared sensor 144-2 and a third one of thepassive infrared sensors 144-3. Zone 5 is the area that is visible onlyto the third passive infrared sensor 144-3. In some embodiments, thedoorbell 130 may be capable of determining the direction that an objectis moving based upon which zones are triggered in a time sequence.

FIG. 14 is a functional block diagram of the components within or incommunication with the doorbell 130, according to an aspect of thepresent embodiments. As described above, the bracket PCB 149 maycomprise an accelerometer 150, a barometer 151, a humidity sensor 152,and a temperature sensor 153. The accelerometer 150 may be one or moresensors capable of sensing motion and/or acceleration. The barometer 151may be one or more sensors capable of determining the atmosphericpressure of the surrounding environment in which the bracket PCB 149 maybe located. The humidity sensor 152 may be one or more sensors capableof determining the amount of moisture present in the atmosphericenvironment in which the bracket PCB 149 may be located. The temperaturesensor 153 may be one or more sensors capable of determining thetemperature of the ambient environment in which the bracket PCB 149 maybe located. As described above, the bracket PCB 149 may be locatedoutside the housing of the doorbell 130 so as to reduce interferencefrom heat, pressure, moisture, and/or other stimuli generated by theinternal components of the doorbell 130.

With further reference to FIG. 14, the bracket PCB 149 may furthercomprise terminal screw inserts 154, which may be configured to receivethe terminal screws 138 and transmit power to the electrical contacts177 on the mounting bracket 137 (FIG. 7). The bracket PCB 149 may beelectrically and/or mechanically coupled to the power PCB 148 throughthe terminal screws 138, the terminal screw inserts 154, the springcontacts 140, and the electrical contacts 177. The terminal screws 138may receive electrical wires located at the surface to which thedoorbell 130 is mounted, such as the wall of a building, so that thedoorbell can receive electrical power from the building's electricalsystem. Upon the terminal screws 138 being secured within the terminalscrew inserts 154, power may be transferred to the bracket PCB 149, andto all of the components associated therewith, including the electricalcontacts 177. The electrical contacts 177 may transfer electrical powerto the power PCB 148 by mating with the spring contacts 140.

With further reference to FIG. 14, the front PCB 146 may comprise alight sensor 155, one or more light-emitting components, such as LED's156, one or more speakers 157, and a microphone 158. The light sensor155 may be one or more sensors capable of detecting the level of ambientlight of the surrounding environment in which the doorbell 130 may belocated. LED's 156 may be one or more light-emitting diodes capable ofproducing visible light when supplied with power. The speakers 157 maybe any electromechanical device capable of producing sound in responseto an electrical signal input. The microphone 158 may be anacoustic-to-electric transducer or sensor capable of converting soundwaves into an electrical signal. When activated, the LED's 156 mayilluminate the light pipe 136 (FIG. 3). The front PCB 146 and allcomponents thereof may be electrically coupled to the power PCB 148,thereby allowing data and/or power to be transferred to and from thepower PCB 148 and the front PCB 146.

The speakers 157 and the microphone 158 may be coupled to the cameraprocessor 170 through an audio CODEC 161. For example, the transfer ofdigital audio from the user's client device 114 and the speakers 157 andthe microphone 158 may be compressed and decompressed using the audioCODEC 161, coupled to the camera processor 170. Once compressed by audioCODEC 161, digital audio data may be sent through the communicationmodule 164 to the network 112, routed by one or more servers 118, anddelivered to the user's client device 114. When the user speaks, afterbeing transferred through the network 112, digital audio data isdecompressed by audio CODEC 161 and emitted to the visitor via thespeakers 157.

With further reference to FIG. 14, the power PCB 148 may comprise apower management module 162, a microcontroller 163 (may also be referredto as “processor,” “CPU,” or “controller”), the communication module164, and power PCB non-volatile memory 165. In certain embodiments, thepower management module 162 may comprise an integrated circuit capableof arbitrating between multiple voltage rails, thereby selecting thesource of power for the doorbell 130. The battery 166, the springcontacts 140, and/or the connector 160 may each provide power to thepower management module 162. The power management module 162 may haveseparate power rails dedicated to the battery 166, the spring contacts140, and the connector 160. In one aspect of the present disclosure, thepower management module 162 may continuously draw power from the battery166 to power the doorbell 130, while at the same time routing power fromthe spring contacts 140 and/or the connector 160 to the battery 166,thereby allowing the battery 166 to maintain a substantially constantlevel of charge. Alternatively, the power management module 162 maycontinuously draw power from the spring contacts 140 and/or theconnector 160 to power the doorbell 130, while only drawing from thebattery 166 when the power from the spring contacts 140 and/or theconnector 160 is low or insufficient. Still further, the battery 166 maycomprise the sole source of power for the doorbell 130. In suchembodiments, the spring contacts 140 may not be connected to a source ofpower. When the battery 166 is depleted of its charge, it may berecharged, such as by connecting a power source to the connector 160.The power management module 162 may also serve as a conduit for databetween the connector 160 and the microcontroller 163.

With further reference to FIG. 14, in certain embodiments themicrocontroller 163 may comprise an integrated circuit including aprocessor core, memory, and programmable input/output peripherals. Themicrocontroller 163 may receive input signals, such as data and/orpower, from the PIR sensors 144, the bracket PCB 149, the powermanagement module 162, the light sensor 155, the microphone 158, and/orthe communication module 164, and may perform various functions asfurther described below. When the microcontroller 163 is triggered bythe PIR sensors 144, the microcontroller 163 may be triggered to performone or more functions. When the light sensor 155 detects a low level ofambient light, the light sensor 155 may trigger the microcontroller 163to enable “night vision,” as further described below. Themicrocontroller 163 may also act as a conduit for data communicatedbetween various components and the communication module 164.

With further reference to FIG. 14, the communication module 164 maycomprise an integrated circuit including a processor core, memory, andprogrammable input/output peripherals. The communication module 164 mayalso be configured to transmit data wirelessly to a remote networkdevice, and may include one or more transceivers (not shown). Thewireless communication may comprise one or more wireless networks, suchas, without limitation, Wi-Fi, cellular, Bluetooth, and/or satellitenetworks. The communication module 164 may receive inputs, such as powerand/or data, from the camera PCB 147, the microcontroller 163, thebutton 133, the reset button 159, and/or the power PCB non-volatilememory 165. When the button 133 is pressed, the communication module 164may be triggered to perform one or more functions. When the reset button159 is pressed, the communication module 164 may be triggered to eraseany data stored at the power PCB non-volatile memory 165 and/or at thecamera PCB memory 169. The communication module 164 may also act as aconduit for data communicated between various components and themicrocontroller 163. The power PCB non-volatile memory 165 may compriseflash memory configured to store and/or transmit data. For example, incertain embodiments the power PCB non-volatile memory 165 may compriseserial peripheral interface (SPI) flash memory.

With further reference to FIG. 14, the camera PCB 147 may comprisecomponents that facilitate the operation of the camera 134. For example,an imager 171 may comprise a video recording sensor and/or a camerachip. In one aspect of the present disclosure, the imager 171 maycomprise a complementary metal-oxide semiconductor (CMOS) array, and maybe capable of recording high definition (e.g., 1080p or better) videofiles. A camera processor 170 may comprise an encoding and compressionchip. In some embodiments, the camera processor 170 may comprise abridge processor. The camera processor 170 may process video recorded bythe imager 171 and audio recorded by the microphone 158, and maytransform this data into a form suitable for wireless transfer by thecommunication module 164 to a network. The camera PCB memory 169 maycomprise volatile memory that may be used when data is being buffered orencoded by the camera processor 170. For example, in certain embodimentsthe camera PCB memory 169 may comprise synchronous dynamic random accessmemory (SD RAM). IR LED's 168 may comprise light-emitting diodes capableof radiating infrared light. IR cut filter 167 may comprise a systemthat, when triggered, configures the imager 171 to see primarilyinfrared light as opposed to visible light. When the light sensor 155detects a low level of ambient light (which may comprise a level thatimpedes the performance of the imager 171 in the visible spectrum), theIR LED's 168 may shine infrared light through the doorbell 130 enclosureout to the environment, and the IR cut filter 167 may enable the imager171 to see this infrared light as it is reflected or refracted off ofobjects within the field of view of the doorbell. This process mayprovide the doorbell 130 with the “night vision” function mentionedabove.

As discussed above, the present disclosure provides numerous examples ofmethods and systems including A/V recording and communication doorbells,but the present embodiments are equally applicable for A/V recording andcommunication devices other than doorbells. For example, the presentembodiments may include one or more A/V recording and communicationsecurity cameras instead of, or in addition to, one or more A/Vrecording and communication doorbells. An example A/V recording andcommunication security camera may include substantially all of thestructure and functionality of the doorbell 130, but without the frontbutton 133, the button actuator, and/or the light pipe 136. An exampleA/V recording and communication security camera may further omit othercomponents, such as, for example, the bracket PCB 149 and itscomponents.

As described above, one aspect of the present embodiments includes therealization that objects may be misplaced, stolen, or kidnapped. Forexample, inanimate objects, such as jewelry, bicycles, vehicles, etc.,or even animate/living objects, such as people or pets, may be removedand/or stolen from a user's premises. It would be advantageous,therefore, if the functionality of A/V recording and communicationdevices could be leveraged to monitor and locate objects, and/oridentify and apprehend suspected thieves and kidnappers. The presentembodiments solve this problem by providing a long-range tag device thatmay be secured to an object (may also be referred to as a “trackedobject”) for monitoring about a user's premises. In various embodiments,the tag device may transmit tag data, where the tag device may becompatible for use in a low-power wide-area network (LPWAN) havinglong-range communications capabilities at a low bit rate. Further, asmart-home hub device and/or a first A/V recording and communicationdevice may be configured to receive the tag data and determine when thetracked object has been removed from the premises using the tag data. Inaddition, a tracked object may be located using the tag device securedto the tracked object. For example, if the tracked object is determinedto be missing and/or stolen, a backend server may transmit the tag datato one or more second A/V recording and communication devices, locatedin various locations. The tracked object may be located when the tagdata associated with the tracked object is captured by one of the secondA/V recording and communication devices. Further, upon locating atracked object, the second A/V recording and communication device maycapture image data of the tracked object and/or the suspected thief ofthe tracked object. These and other aspects and advantages of thepresent embodiments are described in further detail below.

FIG. 15 is a functional block diagram illustrating a system 300 forcommunicating in a network for monitoring and locating tracked objects.In many embodiments, an object may be monitored and located using a tagdevice (may also be referred throughout as a “tag”). In variousembodiments, a tracked object may be associated with a tag having acommunication module for periodically transmitting tag data compatiblefor use in an LPWAN. In many embodiments, the tag data may include anydata compatible for use in an LPWAN, such as (but not limited to) datacompatible with long range, low power wireless technology, such as LoRa®technology developed by Semtech Corporation headquartered in Camarillo,Calif. (may also be referred to as “LoRa data”), or data compatible withany other LPWAN technology, such as SIGFOX, NB IoT, or LTE-M, forexample, or any other LPWAN, or similar, technology now known or laterdeveloped. As further described below, the smart-home hub device may beconfigured to receive the tag data and monitor the tracked object usingthe tag data. In some embodiments, the smart-home hub device may beconfigured to determine when the tracked object has been removed from auser's premises and alert a client device associated with the smart-homehub device (and/or an A/V recording and communication device). Invarious embodiments, the smart-home hub device may transmit to a backenddevice an output signal that includes the tag data and identifies whenthe tracked object is missing and/or stolen. In many embodiments, thebackend devices may transmit a locate object signal that includes thetag data to a plurality of second A/V recording and communicationdevices located throughout the network. In some embodiments, one of theplurality of second A/V recording and communication devices may locatethe tracked object using the tag data, as further described below.Further, upon locating the tracked object, the one of the second A/Vrecording and communication devices may capture second image data thatincludes image data of the tracked object and, potentially, image dataof a suspected perpetrator.

In reference to FIG. 15, the system 300 may include one or more firstaudio/video (A/V) recording and communication devices 302 configured toaccess a first user's network 308 to connect to a network(Internet/PSTN) 310. The system 300 may also include one or more firstclient devices 304, 306, which in various embodiments may be configuredto be in network communication with the first A/V recording andcommunication device 302. The first client devices 304, 306 maycomprise, for example, a mobile phone such as a smartphone, or acomputing device such as a tablet computer, a laptop computer, a desktopcomputer, etc. The first client devices 304, 306 may include any or allof the components and/or functionality of the client device 114 and/orthe client device 800 described herein. In some embodiments, the firstclient devices 304, 306 may not be associated with a first A/V recordingand communication device.

The system 300 may further include a smart-home hub device 301. Thesmart-home hub (also known as a home automation hub) device 301, whichis illustrated in further detail in FIG. 16, may comprise any devicethat facilitates communication with and control of one or more secondarydevices and/or the first A/V recording and communication device 302. Forexample, the smart-home hub may be a component of a home security systemand/or a home automation system (may be a combined homesecurity/automation system). Home automation, or smart home, is buildingautomation for the home. It involves the control and automation ofvarious secondary devices and/or systems, such as lighting, heating(such as smart thermostats), ventilation, air conditioning (HVAC), andsecurity, as well as home appliances, such as washers/dryers, ovens, orrefrigerators/freezers. Examples of secondary security devices in asmart home security/automation system include door sensors, windowsensors, flood sensors, glass break sensors, contact sensors, tiltsensors, temperature sensors, smoke detectors, carbon monoxidedetectors, and lock/unlock sensors. Wi-Fi is often used for remotemonitoring and control of smart home security/automation devices. Smarthome devices, when remotely monitored and controlled via the Internet,may be considered to be components of the Internet of Things. Smart homesystems may include switches and/or sensors connected to a central hub,sometimes called a gateway, from which the system may be controlled witha user interface. The user interface may include any or all of awall-mounted terminal, mobile phone (e.g., smartphone) software, atablet computer or a web interface, often but not always via Internetcloud services. The home automation system may use one or morecommunication protocols, including either or both of wired and wirelessprotocols, including but not limited to X10, Ethernet, RS-485, 6LoWPAN,Bluetooth LE (BLE), ZigBee, and Z-Wave.

The secondary devices may comprise one or more tag device(s) 303 formonitoring and locating one or more tracked object(s) 305, as furtherdescribed below. In some embodiments, the tag device 303 may communicatedirectly with the smart-home hub device 301 and/or the first A/Vrecording and communication device 302 (and/or any other device in thesystem 300). Alternatively, or in addition, the tag device 303 maycommunicate with any device in the system 300, including the smart-homehub device 301, through the first user's network 308. The user maycontrol the tag device 303 through the smart-home hub device 301 usingeither or both of the first client devices 304, 306. For example, theuser may set parameters on the tag device 303 using an applicationexecuting on the first client device 304, which may be, for example, asmartphone. In some embodiments, the user may control the first A/Vrecording and communication device 302 through the smart-home hub device301 using either or both of the first client devices 304, 306.

In various embodiments, the system 300 may also include a plurality ofsecond A/V recording and communication devices 312, 313 connected to thenetwork (Internet/PSTN) 310 using second users' networks 318, 319,respectively, to access the network (Internet/PSTN) 310. The system 300may further include one or more second client devices 314, 316, which invarious embodiments may be configured to be in network communicationwith a second A/V recording and communication device 312. The secondclient devices 314, 316 may comprise, for example, a mobile phone suchas a smartphone, or a computing device such as a tablet computer, alaptop computer, a desktop computer, etc. The second client devices 314,316 may include any or all of the components and/or functionality of theclient device 114 and/or the client device 800 described herein.

In some embodiments, the second A/V recording and communication device313 may not be associated with any second client devices. Such a secondA/V recording and communication device 313 may comprise, for example, apublic or “neighborhood” A/V recording and communication device 313 thatrecords videos that may be accessed by any requesting member of thepublic, and/or by any requesting member of the neighborhood in which thedevice 313 is located, and/or by law enforcement.

In some embodiments, the system 300 may also include one or more thirdparty A/V recording and communication devices 320 connected to thenetwork (Internet/PSTN) 310 using various third party networks 326 suchas a local network, a wireless network such as a cellular/mobile networkand/or a Wi-Fi network, a wired network such as an Ethernet network, apublic network, a low-bandwidth network, and/or any other appropriatenetwork to access the network (Internet/PSTN) 310. The system 300 mayfurther include one or more third party client devices 322, 324, whichin various embodiments may be configured to be in network communicationwith the third party A/V recording and communication device 320. Thethird party client devices 322, 324 may comprise, for example, a mobilephone such as a smartphone, or a computing device such as a tabletcomputer, a laptop computer, a desktop computer, etc. The third partyclient devices 322, 324 may include any or all of the components and/orfunctionality of the client device 114 and/or the client device 800described herein. In some embodiments, the third party client devices322, 324 may not be associated with a third party A/V recording andcommunication device.

With further reference to FIG. 15, the system 300 may also includevarious backend devices such as (but not limited to) storage devices332, backend servers 330, and backend APIs 328 in network communicationwith the first, second, and third party A/V communication devices 302,312, 313, 320 and their respective client devices 304, 306, 314, 316,322, 324. In some embodiments, the storage devices 332 may be a separatedevice from the backend servers 330 (as illustrated) or may be anintegral component of the backend servers 330. In addition, the firstand second users' networks 308, 318, 319 and the network 310 may besimilar in structure and/or function to the user's network 110 and thenetwork 112 (FIG. 1), respectively. In some embodiments, the first andsecond A/V recording and communication devices 302, 312, 313 may besimilar in structure and/or function to the A/V recording andcommunication device 100 (FIG. 1) and/or the A/V recording andcommunication doorbell 130 (FIGS. 3-14). In some embodiments, the firstuser's client devices 304, 306 may be similar in structure and/orfunction to the user's client device 114 (FIG. 1) and/or the user'sclient device 800 (FIG. 26). The second users' client devices 314, 316may also be similar in structure and/or function to the user's clientdevice 114 (FIG. 1) and/or the user's client device 800 (FIG. 26). Also,the storage devices 332 may be similar in structure and/or function tothe storage device 116 (FIG. 1). In addition, in some embodiments, thebackend servers 330 and backend APIs 328 may be similar in structureand/or function to the server 118 and the backend API 120 (FIG. 1),respectively.

FIG. 16 is a functional block diagram illustrating an embodiment of thesmart-home hub device 301 according to various aspects of the presentdisclosure. The smart-home hub device 301 may comprise a processingmodule 412 that is operatively connected to a camera 402, a microphone404, a speaker 406, and a communication module 408. In some embodiments,any or all of the camera 402, the microphone 404, and the speaker 406may be omitted from the smart-home hub device 301. In addition, thecommunication module 408 may include an LPWAN-enabled receiver 410configured to receive tag data 422 from a tag device, as describedabove. For example, in embodiments where the tag data 422 includes LoRadata, the LPWAN receiver 410 may be configured to receive the LoRa data.The processing module 412 may comprise a processor 414, volatile memory416, and non-volatile memory 418 that includes a smart-home hubapplication 420. In various embodiments, the smart-home hub application420 may configure the processor 414 to associate a tag device 303 havingtag data 422 with at least one object to be monitored, as furtherdescribed below. In some embodiments, the smart-home hub application 420may further configure the processor 414 to determine when the at leastone tracked object 305 has been removed from a premises using the tagdata 422, as further described below. In various embodiments, the tagdata 422 may include location data 424 that provides data about thecurrent location of the tag device 303, as further described below. Insome embodiments, the smart-home hub application 420 may furtherconfigure the processor 414 to transmit an alert 426 to a first clientdevice 304, 306 associated with the smart-home hub device 301 and/or thefirst A/V recording and communication device 302 upon a determinationthat the at least one tracked object 305 has been removed from thepremises, as further described below. Further, the smart-home hubapplication 420 may also configure the processor 414 to transmit anoutput signal 428 including the tag data 422 to a backend server 330 forlocating the at least one tracked object 305, as further describedbelow.

FIG. 17 is a functional block diagram illustrating an embodiment of thetag device 303 according to various aspects of the present disclosure.The tag device 303 may comprise a processing module 434 that isoperatively connected to a communication module 430. In someembodiments, the communication module 430 may include an LPWANtransmitter 432 configured to transmit data compatible for use in anLPWAN including data compatible with long range, low power wirelesstechnology such as LoRa data, or data compatible with any other LPWANtechnology, such as SIGFOX, NB IoT, or LTE-M, as described above. InLoRa embodiments, the tag device 303 may also be a LoRa tracker securedto the tracked object 305. The processing module 434 may comprise aprocessor 436, volatile memory 438, and non-volatile memory 440 thatincludes a tag application 442. In various embodiments, the tag device303 may be associated with an object 305 (FIG. 15) designated to bemonitored and located when missing and/or stolen (may also be referredto as “tracked object 305”), as further described below. For example,the tag device 303 may be associated with a tracked object 305 byphysically attaching the tag device 303 to the at least one trackedobject 305. In some embodiments, the tag device 303 may be placed on,within, or in any manner such that the tag device 303 moves and staysconnected to the at least one tracked object 305. Further, thenon-volatile memory 440 may also include tag data 422 that may includelocation data 424 for monitoring and locating tracked objects, asfurther described below.

FIG. 18 is a functional block diagram illustrating an embodiment of thefirst A/V recording and communication device 302 according to variousaspects of the present disclosure. The first A/V recording andcommunication device 302 may comprise a processing module 350 that isoperatively connected to a camera 340, a microphone 342, a speaker 344,and a communication module 346. In some embodiments, the communicationmodule 346 may include an LPWAN receiver 348 that may also beoperatively connected to the processing module 350.

The processing module 350 may comprise a processor 352, volatile memory354, and non-volatile memory 356 that includes a camera application 358.The camera application 358 may configure the processor 352 to capturefirst image data 360 using the camera 340 and first audio data 362 usingthe microphone 342. In various embodiments, the camera application 358may configure the processor 352 to associate a tag device 303 having tagdata 422 with at least one object to be monitored, as further describedbelow. In some embodiments, the camera application 358 may furtherconfigure the processor 352 to determine when the at least one trackedobject 305 has been removed from a premises using the tag data 422, asfurther described. In various embodiments, the tag data 422 may includelocation data 424 that provides data about the current location of thetag device 303, as further described below. In some embodiments, thecamera application 358 may further configure the processor 352 totransmit an alert 364 to a first client device 304, 306 associated withthe first A/V recording and communication device 302 upon adetermination that the at least one tracked object 305 has been removedfrom the premises, as further described below. In some embodiments, thecamera application 358 may further configure the processor 352 totransmit an output signal 366 including the tag data 422 to a backendserver 330 for locating the at least one tracked object 305, as furtherdescribed below.

FIG. 19 is a functional block diagram illustrating an embodiment of thefirst client device(s) 304, 306 according to various aspects of thepresent disclosure. The first client device(s) 304, 306 may include aprocessing module 341 that is operatively connected to a camera 347. Theprocessing module 341 may comprise a processor 343, volatile memory 345,and non-volatile memory 349. The non-volatile memory 349 may include aclient application 351 that configures the processor 343 to capturefirst image data 353 using the camera 347, where the first image data353 includes image data of an object designated to be tracked andlocated when missing. The first client device(s) 304, 306 may alsoinclude a communication module 359 for network communication with thefirst A/V recording and communication device 302 and/or the backendserver 330. In some embodiments, the first client device(s) 304, 306 mayreceive the second image data 390 captured by the second A/V recordingand communication device 312, 313, as described below.

In further reference to FIG. 19, various objects may be designated fortracking and location when missing using the first client device(s) 304,306. For example, the client application 351 may present to a user on adisplay of the first client device(s) 304, 306 a video and/or a stillphoto that contains one or more objects and receives an input from theuser selecting an object to be tracked. In various embodiments, thetracked objects may include inanimate objects and/or animate objects,such as a person or a pet. In some embodiments, the user may designatethe tracked object 305 by selecting an object from the first image data353 captured using the camera 347. Further, the user may designate thetracked object 305 by selecting an object from the first image data 360captured using the camera 340 of the first A/V recording andcommunication device 302. In either embodiment, the tracked object 305may also be associated with the tag data 364, as further describedbelow.

FIG. 20 is a functional block diagram illustrating an embodiment of thesecond A/V recording and communication device(s) 312, 313 according tovarious aspects of the present disclosure. The second A/V recording andcommunication device(s) 312, 313 may comprise a processing module 380that is operatively connected to a camera 370, a microphone 372, aspeaker 374, and a communication module 376. In some embodiments, theprocessing module 380 may also be operatively connected to an LPWANreceiver 378. The processing module 380 may comprise a processor 382,volatile memory 384, and non-volatile memory 386 that includes a cameraapplication 388. The camera application 388 may configure the processor382 to capture second image data 390 using the camera 370 and secondaudio data 392 using the microphone 372. In various embodiments, thecamera application 388 may also configure the processor 382 to transmitthe second image data 390 and/or the second audio data 392 to thebackend server 330, using the communication module 376. In someembodiments, the backend server 330 may locate a tracked object 305using a locate object signal 394 that includes tag data 422 and acommand to locate the tracked object 305 using the tag data 422, asfurther described below. Further, the second A/V recording andcommunication device(s) 312, 313 may also receive a power-up commandsignal 396 that configures the LPWAN receiver 378 to power up from alow-power mode to a powered-on mode to capture the tag data 422 and/orconfigures the camera 370 to power up from a low-power mode to apowered-on mode to capture second image data 390. In some embodiments,the locate object signal 394 and the power-up command signal 396 may becombined and received as a single signal from the backend server 330.

In reference to FIGS. 19 and 20, the image data 360, 390 may compriseimage sensor data such as (but not limited to) exposure values and dataregarding pixel values for a particular sized grid. Further, image datamay comprise converted image sensor data for standard image file formatssuch as (but not limited to) JPEG, JPEG 2000, TIFF, BMP, or PNG. Inaddition, image data may also comprise data related to video, where suchdata may include (but is not limited to) image sequences, frame rates,and the like. Moreover, image data may include data that is analog,digital, uncompressed, compressed, and/or in vector formats. Image datamay take on various forms and formats as appropriate to the requirementsof a specific application in accordance with the present embodiments. Asdescribed herein, the term “record” may also be referred to as “capture”as appropriate to the requirements of a specific application inaccordance with the present embodiments.

FIG. 21 is a functional block diagram illustrating one embodiment of abackend server 330 according to various aspects of the presentdisclosure. The backend server 330 may comprise a processing module 450including a processor 452, volatile memory 454, non-volatile memory 456,and a network interface 464. The network interface 464 may allow thebackend server 330 to access and communicate with devices connected tothe network (Internet/PSTN) 310. For example, the backend server 330 mayreceive an output signal 428, 366 from a smart-home hub device 301and/or a first A/V recording and communication device 302, respectively.In various embodiments, the output signal 428, 366 may include tag data422 for locating a tracked object 305 removed and/or stolen from apremises, as further described below.

In reference to FIG. 21, the non-volatile memory 456 may include aserver application 458 that configures the processor 452 to locatetracked objects, as further described below. In many embodiments, thebackend server 330 may receive an output signal 428 from the smart-homehub device 301 that identifies a tracked object 305 as missing. In otherembodiments, the backend server 330 may receive an output signal 366from the first A/V recording and communication device 302 thatidentifies a tracked object 305 as missing. In some embodiments, thebackend server 330 may locate the tracked object 305 by transmitting alocate object signal 394 to a plurality of second A/V recording andcommunication devices 312, 313, where the locate object signal 394 mayinclude the tag data 422 and a command to locate the tracked object 305using the tag data 422, as further described below. Upon locating thetracked object 305 using the tag data 422, one of the plurality ofsecond A/V recording and communication device(s) 312, 313 may capturesecond image data 390 of the tracked object 305. In some embodiments,the backend server 330 may also generate and transmit a power-up commandsignal 396 to the one of the plurality of second A/V recording andcommunication devices 312, 313 to power up the LPWAN receiver 378 tocapture the tag data 422 and/or to power up the camera 370 to capturethe second image data 390, as further described below. In manyembodiments, the backend server 330 may also generate and transmit anobject found signal 460 to the first client device(s) 304, 306, wherethe object found signal 460 may comprise the second image data 390 thatincludes the image data of the tracked object 305 and/or the locationdata 424 that indicates the location of the tracked object 305.

In further reference to FIG. 21, the non-volatile memory 406 may alsoinclude source identifying data 462 that may be used to determinelocations of the first A/V recording and communication device 302, thesecond A/V recording and communication device(s) 312, 313, and/or thethird party A/V recording and communication device 320. In addition, thesource identifying data 462 may be used to determine locations of thefirst client devices 304, 306, the second client devices 314, 316,and/or the third party client devices 322, 324. In some embodiments, thebackend server 330 may generate and transmit an alert signal 466 thatmay include image data of the tracked object 305, and/or a suspectedperpetrator, and/or possible locations of the tracked object 305, to athird party client device 322, 324 and/or a law enforcement agency, asfurther described below.

In the illustrated embodiment of FIGS. 16-21, the various componentsincluding (but not limited to) the processing modules 412, 434, 350,341, 380, the communication modules 408, 430, 346, 359, 376, and thenetwork interface 464 are represented by separate boxes. The graphicalrepresentations depicted in each of FIGS. 16-21 are, however, merelyexamples, and are not intended to indicate that any of the variouscomponents of the smart-home hub device 301, tag device 303, first A/Vrecording and communication device 302, the second A/V recording andcommunication device(s) 312, 313, or the backend server 330 arenecessarily physically separate from one another, although in someembodiments they might be. In other embodiments, however, the structureand/or functionality of any or all of the components of the smart-homehub device 301 may be combined. In some embodiments, the communicationmodule 376 may include its own processor, volatile memory, and/ornon-volatile memory. Likewise, the structure and/or functionality of anyor all of the components of the tag device 303 may be combined. In someembodiments, the communication module 430 may include its own processor,volatile memory, and/or non-volatile memory. In addition, the structureand/or functionality of any or all of the components of first A/Vrecording and communication device 302 may be combined. In someembodiments the communication module 346 may include its own processor,volatile memory, and/or non-volatile memory. In addition, the structureand/or functionality of any or all of the components of first clientdevice(s) 304, 306 may be combined. In some embodiments, thecommunication module 359 may include its own processor, volatile memory,and/or non-volatile memory. Further, the structure and/or functionalityof any or all of the components of the second A/V recording andcommunication device(s) 312, 313 may be combined. In addition, in someembodiments the communication module 376 may include its own processor,volatile memory, and/or non-volatile memory. Moreover, the structureand/or functionality of any or all of the components of the backendserver 330 may be combined. In addition, in some embodiments the networkinterface 464 may include its own processor, volatile memory, and/ornon-volatile memory.

In further reference to FIGS. 16-21, a communication module, such as thecommunication modules 408, 430, 346, 359, 376 may comprise (but is notlimited to) one or more transceivers and/or wireless antennas (notshown) configured to transmit and receive wireless signals. In furtherembodiments, the communication modules 408, 430, 346, 376 may comprise(but are not limited to) one or more transceivers configured to transmitand receive wired and/or wireless signals. In addition, thecommunication modules 408, 346, 376 may include LPWAN receivers 410,348, 378, and the communication module 430 may include an LPWANtransmitter 432, as described above. In various embodiments, LPWANreceivers and/or transmitters, such as the LPWAN receivers 410, 348, 378and LPWAN transmitter 432, may comprise (but are not limited to) one ormore transceivers and/or wireless antennas (not shown) configured totransmit and receive data compatible for use in an LPWAN, as describedabove.

FIG. 22 is a flowchart illustrating one embodiment of a process 500 formonitoring an object on a premises according to an aspect of the presentdisclosure. In various embodiments, the tracked object 305 may be aninanimate object, such as (but not limited to) a vehicle, a bicycle, awallet, and/or any other personal belonging(s). However, in otherembodiments, the tracked object 305 may be an animate object, such as achild or a pet. In many embodiments, a premises may be equipped with asmart-home hub device 301, as described above. Further, a tag device 303may be placed on or attached to at least one object, allowing a user tomonitor and locate the tracked object 305, as further described below.In many embodiments, the tag device 303 may be configured for use aspart of an LPWAN that allows the tag device 303 to have a relativelylong range, allowing the tag device 303 to transmit tag data 422 thatmay be received even when the tag device 303 has traveled beyond aperimeter of the premises.

In reference to FIG. 22, the process 500 may include securing (blockB502) a tag 303 to at least one object to be tracked. In someembodiments, the tag 303 may be secured directly to the at least onetracked object 305 using any attaching mechanism. For example, the tag303 may be secured to the at least one tracked object 305 using anadhesive, a strap, a clip, magnets, glue, etc. In other embodiments, thetag 303 may be secured to the at least one tracked object 305 by placingthe tag 303 on the at least one tracked object 305 or on an item that isattached to and/or covering the tracked object. The process 500 may alsoinclude associating (block B504) the tag 303 with the at least onetracked object 305. In various embodiments, the tag 303 may have tagdata 422 that includes a unique identifier that may be associated (blockB504) with a particular tracked object 305. In some embodiments, thefirst user may associate (block B504) the tag 303 to the tracked object305 using the smart-home hub device 301. In some embodiments, a firstuser may associate (block B504) the tag 303 to the tracked object 305using first client device(s) 304, 306. In various embodiments, theassociation of the tag 303 to the at least one tracked object 305 may bestored in the non-volatile memory 418 at the smart-home hub device 301.In some embodiments, the association of the tag 303 to the at least onetracked object 305 may be stored in a non-volatile memory 456 of thebackend server 330.

In some embodiments, the process 500 may further include determining(block B506) whether the smart-home hub device 301 is armed. In variousembodiments, the smart-home hub device 301 may have two or more settingsor states, which states may depend, at least in part, on whether thefirst user is on the premises or not. For example, when the first useris on the premises, the smart-home hub device 301 may be disarmed, ormay be in an armed-stay state (may also be referred to as “armed-home”).When the first user is not on the premises, the smart-home hub device301 may be in an armed-away state. In further reference to the process500, if the smart-home hub device 301 is not armed (block B506) theprocess 500 may not proceed any further until the smart-home hub device301 is armed. If, however, the smart-home hub device 301 is armed (blockB506), then the process 500 may proceed to block B508, which isdescribed below. In other embodiments, the process 500 may continueregardless of the armed/disarmed state of the smart-home hub device 301.In other words, block B506 may be omitted from some embodiments.

In further reference to the process 500, the smart-home hub device 301may listen (block B508) for tag data 422 transmitted by the tag 303secured to the at least one tracked object 305. As described above, thetag 303 may include a communication module 430 having an LPWANtransmitter 432 for transmitting the tag data 422. Further, thesmart-home hub device 301 may include a communication module 408 havingan LPWAN receiver 410 for listening (block B508) for the tag data 422 byreceiving the tag data 422 transmitted by the tag 303. In someembodiments, the tag 303 may be configured to transmit the tag data 422using chirp spread spectrum (CSS) modulation techniques and thesmart-home hub device 301 may be configured to receive (block B508) thetag data 422 using CSS demodulation techniques. In some embodiments, thetag data may be LoRa data where the tag 303 may be a LoRa trackerconfigured to transmit the LoRa data. In such embodiments, thesmart-home hub device 301 may be configured to receive (block B508) LoRadata. In other embodiments, the tag 303 may be configured to transmitthe tag data 422 using ultra narrowband (UNB) modulation techniques andthe smart-home hub device 301 may be configured to receive (block B508)the tag data 422 using UNB demodulation techniques.

In further reference to FIG. 22, the process 500 may further includedetermining (block B510) whether the at least one tracked object 305 hasbeen removed from the premises using the tag data 422, as furtherdescribed below. If the at least one tracked object 305 has not beenremoved (block B510), then the process 500 may continue to listen (blockB508) for tag data 422 from the tag 303 secured to the at least onetracked object 305. However, if the tracked object 305 has been removedfrom the premises (block B508), then the smart-home hub device 301 maygenerate and transmit (block B512) an alert 426 to the first clientdevice(s) 304, 306 associated with the smart-home hub device 301 and/orthe first A/V recording and communication device 302. The alert 426 maycomprise a notification that the at least one tracked object 305 hasbeen removed from the premises. In some embodiments, the process 500 mayalso include the smart-home hub device 301 generating and transmitting(block B514) an output signal 428 to the backend server 330, wherein theoutput signal 428 includes the tag data 422 and identifies the at leastone tracked object 305 as missing.

FIG. 23 is a flowchart illustrating one embodiment of a process 520 fordetermining (block B510, FIG. 22) whether a tracked object has beenremoved from a premises according to an aspect of the presentdisclosure. The process 520 may include the smart-home hub device 301receiving (block B522) tag data 422 that includes location data 424 fromthe tag 303 secured to the at least one tracked object 305. In variousembodiments, the location data 424 may include (but is not limited to)GPS signals, data from various device sensors of the tag device 303,Wi-Fi access points, and cell tower IDs that can be used to derive orestimate the current location of the tag 303. The process 520 mayfurther include determining (block B524) if the location of the tag 303is beyond a perimeter of the premises. In some embodiments, theperimeter of the premises may be set by the first user using the firstclient device(s) 304, 306 and/or the smart-home hub device 301. In someembodiments, the perimeter may be set by default to a particular sizeand shape. In other embodiments, the perimeter may be set based on theat least one tracked object 305 where the perimeter shape and size maybe dependent on the particular tracked object 305. If the location ofthe tag 303 is not beyond (block B524) the perimeter, then the process520 may continue to receive (block B522) tag data 422 including locationdata 424 from the tag 303 secured to the at least one tracked object305. However, if the location of the tag 303 is beyond (block B524) theperimeter, then the process 520 may conclude (block B526) that thetracked object 305 has been removed from the premises (block B510). Ofcourse, even if the process 520 advances to block B526, the process 520may continue to receive (block B522) tag data 422 including locationdata 424 from the tag 303 secured to the at least one tracked object305, at least until the tag 303 moves out of communication range withrespect to the smart-home hub device 301.

FIG. 24 is a flowchart illustrating another embodiment of a process 530for determining (block B510, FIG. 22) whether a tracked object has beenremoved from a premises according to an aspect of the presentdisclosure. The process 530 may include the smart-home hub device 301receiving (block B532) tag data 422 that includes location data 424 fromthe tag 303 secured to the at least one tracked object 305. In variousembodiments, the location data 424 may be used to derive or estimate alocation of the tag 303 at a first time and at subsequent times. Basedon the location of the tag 303 at various times, the direction ofmovement of the tag 303 can be ascertained. The process 530 may furtherinclude determining (block B534) if the direction of movement of the tag303 is away from the smart-home hub device 301. If the tag 303 is notmoving away from the smart-home hub device 301 (block B534), then theprocess 530 may continue to receive (block B532) tag data 422 includinglocation data 424 from the tag 303 secured to the at least one trackedobject 305. However, if the tag 303 is moving away from the smart-homehub device 301 (block B534), then the process 530 may conclude (blockB536) that the tracked object 305 has been removed from the premises(block B510). In some embodiments, the direction of movement of the tagmay be referenced based on any location such as the first A/V recordingand communication device 302 or any other known stationary location.Further, in some embodiments, the direction of movement may have toreach some threshold amount of movement before determining (block B534)that the direction of movement of the tag 303 is or is not away from thesmart-home hub device 301. Of course, even if the process 530 advancesto block B536, the process 530 may continue to receive (block B532) tagdata 422 including location data 424 from the tag 303 secured to the atleast one tracked object 305, at least until the tag 303 moves out ofcommunication range with respect to the smart-home hub device 301.

FIG. 25 is a flowchart illustrating another embodiment of a process 540for determining (block B510, FIG. 22) whether a tracked object has beenremoved from a premises according to an aspect of the presentdisclosure. The process 540 may include the smart-home hub device 301listening (block B542) for tag data 422 from the tag 303 secured to theat least one tracked object 305. The process 540 may further includewaiting (block B544) for a predetermined time-out period to receive thetag data 422. If the tag data 422 is received within the predeterminedtime-out period (block B544), then the process 540 may continue tolisten (block B542) for the tag data 422 from the tag 303 secured to theat least one tracked object 305. However, if the tag data 422 is notreceived within the predetermined time-out period (block B544), then theprocess 540 may conclude (block B546) that the tracked object 305 hasbeen removed from the premises (block B510). In some embodiments, thepredetermined time-out period may be any length of time. In variousembodiments, the predetermined time-out period may be set by the firstuser using the first client device(s) 304, 306 and/or the smart-home hubdevice 301. In some embodiments, the predetermined time-out period maybe set by default to a particular length. In further embodiments, thepredetermined time-out period may be dependent on the particular trackedobject 305.

FIG. 26 is a flowchart illustrating one embodiment of a process 550 formonitoring and locating a tracked object according to an aspect of thepresent disclosure. The process 550 may include receiving (block B552)from the smart-home hub device 301 an output signal 428 that includesthe tag data 422 and identifies at least one the tracked object 305 asmissing. In other embodiments, the process 550 may include receiving(block B552), from the first A/V recording and communication device 302an output signal 366 that includes the tag data 422 and identifies atleast one the tracked object 305 as missing. Upon receiving (block B552)the output signal 428, 366, the process 550 may include transmitting(block B554) a locate object signal 394 from the backend server 330 to aplurality of second A/V recording and communication devices 312, 313. Invarious embodiments, the locate object signal 394 may include the tagdata 422 and a command to locate the tracked object 305 using the tagdata 422. For example, in embodiments where the tag data 422 includesLoRa data, at least some of the plurality of second A/V recording andcommunication devices 312, 313 may include a communication module 376including an LPWAN receiver 378 configured to receive LoRa data. Invarious embodiments, the tag 303, such as a LoRa tracker, secured to theat least one tracked object 305 may periodically transmit a signalreceived by the communication module 376. In various embodiments, thetransmitted signal from the tag 303, such as the LoRa tracker, mayinclude a variety of data including (but not limited to) location data424 that may be used to derive and/or determine the current location ofthe tag 303 and thus the tracked object 305. The tracked object 305 maybe located when one of the plurality of second A/V recording andcommunication devices 312, 313 captures LoRa data (or has LoRa datastored) that matches the LoRa data associated with the tracked object305.

In further reference to FIG. 26, the one of the plurality of second A/Vrecording and communication devices 312, 313 may capture second imagedata 390 using the camera 370 upon locating the tracked object 305. Insome embodiments, the backend server 330 may transmit (block B556) apower-up command signal 396 to one of the plurality of second A/Vrecording and communication devices 312, 313, wherein the power-upcommand signal 396 configures the one of the plurality of second A/Vrecording and communication devices 312, 313 to power up the LPWANreceiver 378 to capture the tag data 422 and/or to power up the camera370 to capture second image data 390 that includes image data of thetracked object 305. The process 550 may include receiving (block B558)the second image data 390 that includes image data of the tracked object305, from one of the plurality of second A/V recording and communicationdevices 312, 313. In addition, the process 550 may also includegenerating and transmitting (block B560) an object found signal 460 tothe first client device(s) 304, 306. In some embodiments, the objectfound signal 460 may include the second image data 390 that includes theimage data of the tracked object 305, and/or the location data 424 thatincludes the location of the tracked object 305. In some embodiments,the second image data 390 may also include image data of a suspectedthief of the tracked object 305 captured using the camera 370 of the oneof the plurality of second A/V recording and communication devices 312,313. In some embodiments, the location of the tracked object 305 may bedetermined at the backend server 330 using the source identifying data462, which, as described above, may be used to determine the location(s)of the second A/V recording and communication device(s) 312, 313.

FIG. 27 is a flowchart illustrating one embodiment of a process 570 forcapturing image data 390 of a tracked object according to an aspect ofthe present disclosure. The process 570 may include at least one secondA/V recording and communication device 312, 313, receiving (block B572)a locate object signal 394 from a backend server 330, as describedabove. In various embodiments, the locate object signal 394 may includetag data 422 and a command to locate a tracked object 305 associatedwith the tag data 422, as described above. In some embodiments, theprocess 570 may include receiving (block B574) a power-up command signal396 that configures a processor 382 of the second A/V recording andcommunication device 312, 313 to power up (block B576) the LPWANreceiver 378 and/or the camera 370 from a low-power mode to a powered-onmode, as described above. The process 570 may also include locating(block B578) a tracked object 305 using the tag data 422, as describedabove. Upon locating the tracked object 305, the second A/V recordingand communication device(s) 312, 313 may capture (block B580) secondimage data 390 that includes image data of the tracked object 305 usingthe camera 370. As described above, the second image data 390 may alsoinclude image data of a suspected thief associated with the trackedobject 305. Further, the process 570 may also include transmitting(block B582) the second image data 390 that includes the image data ofthe tracked object 305 (and, in some embodiments, the suspected thief)to the backend server 330.

In some of the present embodiments, including, for example, theprocesses 550, 570 of FIGS. 26 and 27, one aspect may comprise acquiringpermissions. The plurality of second A/V recording and communicationdevices 312 may be owned by and/or associated with user(s) other thanthe user associated with the tracked object 305. Thus, one aspect of thepresent embodiments may comprise acquiring permissions from theowner(s)/user(s) of the second A/V recording and communication devices312 to access videos recorded by those devices 312, and/or acquiringpermissions from the owner(s)/user(s) of the second A/V recording andcommunication devices 312 to send to such devices 312 the locate objectsignal 394 and to command such devices 312 to record videos in responseto receiving the locate object signal 394. In some embodiments, thesecond A/V recording and communication devices 313, which are public or“neighborhood” cameras, may be accessed without first acquiringpermissions.

In one example embodiment, acquiring permissions from theowner(s)/user(s) of the second A/V recording and communication devices312 may comprise requesting and obtaining blanket permissions to accessany videos recorded by the devices 312 in response to the devices 312receiving the locate object signal 394 from the backend server 330,and/or to send to such devices 312 the locate object signal 394 and tocommand such devices 312 to record videos in response to receiving thelocate object signal 394. Such blanket permissions may be requested andobtained, for example, at the time each of the second A/V recording andcommunication devices 312 is first set up by their respectiveowners/users, where the blanket permission is requested and obtainedduring one or more steps in setting up the devices 312. Alternatively,the blanket permissions may be requested and obtained from theowner(s)/user(s) of the second A/V recording and communication devices312 at any time during the operational life of such devices 312. Blanketpermissions may be requested and obtained, for example, through one ormore requests (e.g., push notifications) sent to the client devices 314,316 associated with the second A/V recording and communication devices312.

In another example embodiment, acquiring permissions from theowner(s)/user(s) of the second A/V recording and communication devices312 may comprise requesting and obtaining limited permissions to accessonly specific videos recorded by the devices 312 in response to thedevices 312 receiving the locate object signal 394 from the backendserver 330, and/or to send to such devices 312 the locate object signal394 and to command such devices 312 to record videos in response toreceiving the locate object signal 394. Such limited permissions may berequested and obtained, for example, in response to receiving the outputsignal 428 from the smart-home hub device 301 (and/or the output signal366 from the first A/V recording and communication device 302)indicating that a tracked object 305 is missing. Limited permissions maybe requested and obtained, for example, through one or more requests(e.g., push notifications) sent to the client devices 314, 316associated with the second A/V recording and communication devices 312.For example, when a tracked object 305 is reported missing through thelocate object signal 394 sent to the backend server 330, requests forlimited permissions may be sent to the client devices 314, 316associated with the second A/V recording and communication devices 312,where the second A/V recording and communication devices 312 are locatedwithin a certain distance of the smart-home hub device 301 that sent theoutput signal 428 (and/or the first A/V recording and communicationdevice 302 that sent the output signal 366). Such requests for limitedpermissions may comprise, for example, push notifications, or any othertype of communication. After obtaining limited permissions from at leastsome of the owners/users of the second A/V recording and communicationdevices 312 located within the certain distance of the smart-home hubdevice 301 that sent the output signal 428 (and/or the first A/Vrecording and communication device 302 that sent the output signal 366),the backend server 330 may send the locate object signal 394 to the atleast some of the second A/V recording and communication devices 312 forwhich the limited permissions have been obtained. Those devices 312 maysubsequently record image data (e.g., videos) when the LPWAN receivers378 of such devices 312 detect the tag 303 associated with the missingtracked object 305. The recorded image data may then be sent by thesecond A/V recording and communication devices 312 to the backend server330 and shared with the first client device 304, 306, as describedabove.

FIG. 28 is a sequence diagram illustrating an embodiment of a process600 for locating missing and/or stolen objects according to variousaspects of the present disclosure. The process 600 may include a tagdevice 303, a smart-home hub device 301, a first client device(s) 304,306, a backend device, such as a backend server 330, and a second A/Vrecording and communication device(s) 312, 313. At a time T₁, theprocess 600 may include the tag 303 sending tag data 422 to thesmart-home hub device 301. In various embodiments, the tag data 422 mayinclude location data 424, as described above. Further, the tag 303 maybe associated with at least one tracked object 305 by the smart-home hubdevice 301 for monitoring about a premises, as further described above.Upon a determination that the at least one tracked object 305 has beenremoved from the premises, at a time T₂, the smart-home hub device 301may transmit an alert signal 426 to the first client device(s) 304, 306,as described above. At a time T₃, the smart-home hub device 301 maytransmit an output signal 428 that includes the tag data 422 andidentifies at least one tracked object 305 as missing to the backendserver 330, as described above. In other embodiments, the smart-home hubdevice 301 may transmit the output signal 428 to the backend server 330at the same time as, or before, transmitting the alert signal 426 to thefirst client device(s) 304, 306. At a time T₄, the backend server 330may transmit to one or more of the second A/V recording andcommunication device(s) 312, 313 a locate object signal 394 thatincludes the tag data 422 and a command to locate the tracked object 305using the tag data 422, as described above. In many embodiments, thesecond A/V recording and communication device(s) 312, 313 may locate theat least one tracked object 305 using the tag data 422 and capture imagedata, such as the second image data 390, using a camera 370. In someembodiments, the backend server 330 may also transmit a power-up commandsignal 396 that configures the LPWAN receiver 378 and/or the camera 370of the second A/V recording and communication device(s) 312, 313 tofirst power up and then capture the tag data 422 and the second imagedata 390, respectively. Upon locating the tracked object 305 andcapturing the second image data 390, the second A/V recording andcommunication device(s) 312, 313 may transmit the second image data 390to the backend server 330 at a time T₅. The backend server 330 maygenerate and transmit an object found signal 460 to the first clientdevice(s) 304, 306 at a time T₆. In many embodiments, the object foundsignal 460 may include the second image data 390, where the second imagedata 390 may include image data of the tracked object 305 (and, in someembodiments, a suspected thief), and/or the location data 424 thatincludes the location of the tracked object 305, as described above.

FIG. 29 is a sequence diagram illustrating another embodiment of aprocess 650 for locating missing and/or stolen objects according tovarious aspects of the present disclosure. In some embodiments, a firstA/V recording and communication device 302 may monitor a tracked object305 on a premises. The process 650 may include a tag device 303, a firstA/V recording and communication device 302, a first client device(s)304, 306, a backend device, such as a backend server 330, and a secondA/V recording and communication device(s) 312, 313. At a time T₁, theprocess may include the tag 303 sending tag data 422 to the first A/Vrecording and communication device 302. In various embodiments, the tagdata 422 may include location data 424, as described above. Further, thetag 303 may be associated with at least one tracked object 305 by thefirst A/V recording and communication device 302 for monitoring about apremises, as further described above. In many embodiments, the first A/Vrecording and communication device 302 may determine when the at leastone tracked object 305 has been removed from the premises using similarprocesses used by a smart-home hub device 301, as described above. Upona determination that the at least one tracked object 305 has beenremoved from the premises, at a time T₂, the first A/V recording andcommunication device 302 may transmit an alert signal 364 to the firstclient device(s) 304, 306 associated with the first A/V recording andcommunication device 302, as described above. At a time T₃, the firstA/V recording and communication device 302 may transmit an output signal366 that includes the tag data 422 and identifies the at least onetracked object 305 as missing to the backend server 330, as describedabove. In other embodiments, the first A/V recording and communicationdevice 302 may transmit the output signal 366 to the backend server 330at the same time as, or before, transmitting the alert signal 364 to thefirst client device(s) 304, 306. At a time T₄, the backend server 330may transmit to one or more of the second A/V recording andcommunication device(s) 312, 313 a locate object signal 394 thatincludes the tag data 422 and a command to locate the tracked object 305using the tag data 422, as described above. In many embodiments, thesecond A/V recording and communication device(s) 312, 313 may locate theat least one tracked object 305 using the tag data 422 and capturesecond image data 390 using a camera 370. In some embodiments, thebackend server 330 may also transmit a power-up command signal 396 thatconfigures the LPWAN receiver 378 and/or the camera 370 of the secondA/V recording and communication device(s) 312, 313 to first power up andthen capture the tag data 422 and the second image data 390,respectively. Upon locating the tracked object 305 and capturing thesecond image data 390, the second A/V recording and communicationdevice(s) 312, 313 may transmit the second image data 390 to the backendserver 330 at a time T₅. The backend server 330 may generate andtransmit an object found signal 460 to the first client device(s) 304,306 at a time T₆. In many embodiments, the object found signal 460 mayinclude the second image data 390, where the second image data 390 mayinclude image data of the tracked object 305 (and, in some embodiments,a suspected thief), and/or the location data 424 that includes thelocation of the tracked object 305, as described above.

FIG. 30 is a functional block diagram of a client device 800 on whichthe present embodiments may be implemented according to various aspectsof the present disclosure. The user's client device 114 described withreference to FIG. 1 may include some or all of the components and/orfunctionality of the client device 800. The client device 800 maycomprise, for example, a smartphone.

With reference to FIG. 30, the client device 800 includes a processor802, a memory 804, a user interface 806, a communication module 808, anda dataport 810. These components are communicatively coupled together byan interconnect bus 812. The processor 802 may include any processorused in smartphones and/or portable computing devices, such as an ARMprocessor (a processor based on the RISC (reduced instruction setcomputer) architecture developed by Advanced RISC Machines (ARM).). Insome embodiments, the processor 802 may include one or more otherprocessors, such as one or more conventional microprocessors, and/or oneor more supplementary co-processors, such as math co-processors.

The memory 804 may include both operating memory, such as random accessmemory (RAM), as well as data storage, such as read-only memory (ROM),hard drives, flash memory, or any other suitable memory/storage element.The memory 804 may include removable memory elements, such as aCompactFlash card, a MultiMediaCard (MMC), and/or a Secure Digital (SD)card. In some embodiments, the memory 804 may comprise a combination ofmagnetic, optical, and/or semiconductor memory, and may include, forexample, RAM, ROM, flash drive, and/or a hard disk or drive. Theprocessor 802 and the memory 804 each may be, for example, locatedentirely within a single device, or may be connected to each other by acommunication medium, such as a USB port, a serial port cable, a coaxialcable, an Ethernet-type cable, a telephone line, a radio frequencytransceiver, or other similar wireless or wired medium or combination ofthe foregoing. For example, the processor 802 may be connected to thememory 804 via the dataport 810.

The user interface 806 may include any user interface or presentationelements suitable for a smartphone and/or a portable computing device,such as a keypad, a display screen, a touchscreen, a microphone, and aspeaker. The communication module 808 is configured to handlecommunication links between the client device 800 and other, externaldevices or receivers, and to route incoming/outgoing data appropriately.For example, inbound data from the dataport 810 may be routed throughthe communication module 808 before being directed to the processor 802,and outbound data from the processor 802 may be routed through thecommunication module 808 before being directed to the dataport 810. Thecommunication module 808 may include one or more transceiver modulescapable of transmitting and receiving data, and using, for example, oneor more protocols and/or technologies, such as GSM, UMTS (3GSM), IS-95(CDMA one), IS-2000 (CDMA 2000), LTE, FDMA, TDMA, W-CDMA, CDMA, OFDMA,Wi-Fi, WiMAX, or any other protocol and/or technology.

The dataport 810 may be any type of connector used for physicallyinterfacing with a smartphone and/or a portable computing device, suchas a mini-USB port or an IPHONE®/IPOD® 30-pin connector or LIGHTNING®connector. In other embodiments, the dataport 810 may include multiplecommunication channels for simultaneous communication with, for example,other processors, servers, and/or client terminals.

The memory 804 may store instructions for communicating with othersystems, such as a computer. The memory 804 may store, for example, aprogram (e.g., computer program code) adapted to direct the processor802 in accordance with the present embodiments. The instructions alsomay include program elements, such as an operating system. Whileexecution of sequences of instructions in the program causes theprocessor 802 to perform the process steps described herein, hard-wiredcircuitry may be used in place of, or in combination with,software/firmware instructions for implementation of the processes ofthe present embodiments. Thus, the present embodiments are not limitedto any specific combination of hardware and software.

FIG. 31 is a functional block diagram of a general-purpose computingsystem on which the present embodiments may be implemented according tovarious aspects of the present disclosure. The computer system 900 maybe embodied in at least one of a personal computer (also referred to asa desktop computer) 900A, a portable computer (also referred to as alaptop or notebook computer) 900B, and/or a server 900C. A server is acomputer program and/or a machine that waits for requests from othermachines or software (clients) and responds to them. A server typicallyprocesses data. The purpose of a server is to share data and/or hardwareand/or software resources among clients. This architecture is called theclient-server model. The clients may run on the same computer or mayconnect to the server over a network. Examples of computing serversinclude database servers, file servers, mail servers, print servers, webservers, game servers, and application servers. The term server may beconstrued broadly to include any computerized process that shares aresource to one or more client processes.

The computer system 900 may execute at least some of the operationsdescribed above. The computer system 900 may include at least oneprocessor 910, memory 920, at least one storage device 930, andinput/output (I/O) devices 940. Some or all of the components 910, 920,930, 940 may be interconnected via a system bus 950. The processor 910may be single- or multi-threaded and may have one or more cores. Theprocessor 910 may execute instructions, such as those stored in thememory 920 and/or in the storage device 930. Information may be receivedand output using one or more I/O devices 940.

The memory 920 may store information, and may be a computer-readablemedium, such as volatile or non-volatile memory. The storage device(s)930 may provide storage for the system 900, and may be acomputer-readable medium. In various aspects, the storage device(s) 930may be a flash memory device, a hard disk device, an optical diskdevice, a tape device, or any other type of storage device.

The I/O devices 940 may provide input/output operations for the system900. The I/O devices 940 may include a keyboard, a pointing device,and/or a microphone. The I/O devices 940 may further include a displayunit for displaying graphical user interfaces, a speaker, and/or aprinter. External data may be stored in one or more accessible externaldatabases 960.

The features of the present embodiments described herein may beimplemented in digital electronic circuitry, and/or in computerhardware, firmware, software, and/or in combinations thereof. Featuresof the present embodiments may be implemented in a computer programproduct tangibly embodied in an information carrier, such as amachine-readable storage device, and/or in a propagated signal, forexecution by a programmable processor. Embodiments of the present methodsteps may be performed by a programmable processor executing a programof instructions to perform functions of the described implementations byoperating on input data and generating output.

The features of the present embodiments described herein may beimplemented in one or more computer programs that are executable on aprogrammable system including at least one programmable processorcoupled to receive data and/or instructions from, and to transmit dataand/or instructions to, a data storage system, at least one inputdevice, and at least one output device. A computer program may include aset of instructions that may be used, directly or indirectly, in acomputer to perform a certain activity or bring about a certain result.A computer program may be written in any form of programming language,including compiled or interpreted languages, and it may be deployed inany form, including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment.

Suitable processors for the execution of a program of instructions mayinclude, for example, both general and special purpose processors,and/or the sole processor or one of multiple processors of any kind ofcomputer. Generally, a processor may receive instructions and/or datafrom a read only memory (ROM), or a random access memory (RAM), or both.Such a computer may include a processor for executing instructions andone or more memories for storing instructions and/or data.

Generally, a computer may also include, or be operatively coupled tocommunicate with, one or more mass storage devices for storing datafiles. Such devices include magnetic disks, such as internal hard disksand/or removable disks, magneto-optical disks, and/or optical disks.Storage devices suitable for tangibly embodying computer programinstructions and/or data may include all forms of non-volatile memory,including for example semiconductor memory devices, such as EPROM,EEPROM, and flash memory devices, magnetic disks such as internal harddisks and removable disks, magneto-optical disks, and CD-ROM and DVD-ROMdisks. The processor and the memory may be supplemented by, orincorporated in, one or more ASICs (application-specific integratedcircuits).

To provide for interaction with a user, the features of the presentembodiments may be implemented on a computer having a display device,such as an LCD (liquid crystal display) monitor, for displayinginformation to the user. The computer may further include a keyboard, apointing device, such as a mouse or a trackball, and/or a touchscreen bywhich the user may provide input to the computer.

The features of the present embodiments may be implemented in a computersystem that includes a back-end component, such as a data server, and/orthat includes a middleware component, such as an application server oran Internet server, and/or that includes a front-end component, such asa client computer having a graphical user interface (GUI) and/or anInternet browser, or any combination of these. The components of thesystem may be connected by any form or medium of digital datacommunication, such as a communication network. Examples ofcommunication networks may include, for example, a LAN (local areanetwork), a WAN (wide area network), and/or the computers and networksforming the Internet.

The computer system may include clients and servers. A client and servermay be remote from each other and interact through a network, such asthose described herein. The relationship of client and server may ariseby virtue of computer programs running on the respective computers andhaving a client-server relationship to each other.

The above description presents the best mode contemplated for carryingout the present embodiments, and of the manner and process of practicingthem, in such full, clear, concise, and exact terms as to enable anyperson skilled in the art to which they pertain to practice theseembodiments. The present embodiments are, however, susceptible tomodifications and alternate constructions from those discussed abovethat are fully equivalent. Consequently, the present invention is notlimited to the particular embodiments disclosed. On the contrary, thepresent invention covers all modifications and alternate constructionscoming within the spirit and scope of the present disclosure. Forexample, the steps in the processes described herein need not beperformed in the same order as they have been presented, and may beperformed in any order(s). Further, steps that have been presented asbeing performed separately may in alternative embodiments be performedconcurrently. Likewise, steps that have been presented as beingperformed concurrently may in alternative embodiments be performedseparately.

What is claimed is:
 1. A method for monitoring an object using asmart-home hub device in network communication with audio/video (AN)recording and communication devices, the method comprising: associating,by the smart-home hub device, a tag having tag data compatible for usein a low-power wide-area network (LPWAN) with at least one trackedobject, wherein the tag is configured to transmit the tag data over afrequency compatible with the LPWAN using a communication module;powering up the smart-home hub device to monitor the at least onetracked object on a premises by in response to a locate object signaland listening for the tag data transmitted by the tag, wherein thesmart-home hub device listens for the tag data using an LPWAN receiverconfigured to receive the tag data, and wherein the locate object signalcomprises an instruction to power up the communication module thatconfigures the communication module to listen for the tag datatransmitted by the tag; determining that the at least one tracked objecthas been removed from the premises using the tag data; and transmitting,from the smart-home hub device, to a first client device associated witha first A/V recording and communication device, an alert upon adetermination that the at least one tracked object has been removed fromthe premises.
 2. The method of claim 1, further comprising receiving thetag data, from the tag, at the smart-home hub device, wherein the tagdata includes location data.
 3. The method of claim 1, furthercomprising receiving the tag data, from the tag, at the smart-home hubdevice, wherein the tag data includes location data, and the locationdata indicates that the tag is moving away from the smart-home hubdevice.
 4. The method of claim 1, wherein the tag is configured totransmit the tag data using chirp spread spectrum (CSS) modulationtechniques.
 5. The method of claim 4, wherein the smart-home hub devicecomprises a communication module configured to receive the tag datausing CSS demodulation techniques.
 6. The method of claim 5, wherein thetag data is LoRa data.
 7. The method of claim 6, wherein the tag is aLoRa tracker configured to transmit the LoRa data.
 8. The method ofclaim 7, wherein the smart-home hub device comprises a communicationmodule configured to receive LoRa data.
 9. The method of claim 1,wherein the tag is configured to transmit the tag data using ultranarrowband (UNB) modulation techniques.
 10. The method of claim 9,wherein the smart-home hub device comprises a communication moduleconfigured to receive the tag data using UNB demodulation techniques.11. The method of claim 1, further comprising transmitting, from thesmart-home hub device, to a backend server, an output signal thatincludes the tag data and identifies the at least one tracked object asmissing.
 12. A method for monitoring an object using audio/videorecording and communication devices (A/V devices), the methodcomprising: receiving, from a smart-home hub device associated with afirst user, at a server, an output signal that includes tag datacompatible for use in a low-power wide-area network (LPWAN), wherein theoutput signal identifies at least one tracked object as missing;transmitting, from the server, to a plurality of A/V devices each havinga communication module configured to receive the tag data over afrequency compatible with the LPWAN and each being associated with oneor more users other than the first user, a locate object signal thatcomprises: the tag data, and an instruction to power up thecommunication module from a low-power mode to a powered-on mode, whereinthe instruction to power up the communication module configures thecommunication module to listen for the tag data transmitted by a tag;receiving, from one of the plurality of A/V devices, image data of theat least one tracked object captured using a camera of the one of theplurality of A/V devices; and transmitting, from the server to a clientdevice associated with the smart-home hub device, an object found signalcomprising the image data of the at least one tracked object.
 13. Themethod of claim 12, wherein the locate object signal further comprisesan instruction to power up the camera and capture the image data of theat least one tracked object.
 14. The method of claim 13, wherein theimage data includes images of a person who has removed the at least onetracked object from a premises.
 15. The method of claim 12, wherein thecommunication module is further configured to receive the tag data usingchirp spread spectrum (CSS) demodulation techniques.
 16. The method ofclaim 15, wherein the tag data is LoRa data.
 17. The method of claim 16,wherein the communication module is further configured to receive LoRadata.
 18. The method of claim 12, wherein the communication module isfurther configured to receive tag data using ultra narrowband (UNB)demodulation techniques.
 19. A method for locating a missing objectusing an audio/video recording and communication device (A/V device),the A/V device including a camera and a communication module, the methodcomprising: receiving, from a server, using the communication module, alocate object signal comprising tag data compatible for use in alow-power wide-area network (LPWAN) and an instruction to power up thecommunication module of the A/V device from a low-power mode to apowered-on mode, wherein the instruction to power up the communicationmodule configures the communication module to listen for the tag datatransmitted by a tau; powering up the communication module based on thereceiving of the locate object signal, wherein the communication modulecomprises an LPWAN receiver configured to receive the tag data;listening for, and detecting, using the communication module, the tagdata transmitted by the tag over a frequency compatible with the LPWAN;recording, using the camera, image data that includes image data of thetracked object; and transmitting, to the server, an object found signalcomprising the image data that includes the image data of the trackedobject.
 20. The method of claim 19, wherein the power-up command signalfurther configures the A/V device to power up the camera and capture theimage data that includes the image data of the tracked object.
 21. Themethod of claim 20, wherein the image data includes images of a personwho has removed the tracked object from a premises.
 22. The method ofclaim 19, wherein: the listening for, and detecting, the tag data occursin response to receiving the locate object signal; and the recording,using the camera, image data that includes image data of the trackedobject occurs in response to detecting the tag data.
 23. The method ofclaim 1, wherein the determining that the at least one tracked objecthas been removed from the premises using the tag data comprisesdetermining that the tag data transmitted by the tag is not received bythe smart-home hub device within a user-specified predetermined time-outperiod.
 24. The method of claim 1, wherein the determining that the atleast one tracked object has been removed from the premises using thetag data comprises determining that the tag data transmitted by the tagis not received by the smart-home hub device within an item specificpredetermined time-out period.